Re: [Fwd: Client Services crash logs]

[muppet <scott asofyet org>]

On May 27, 2008, at 1:09 AM, Daniel Kasak wrote:

> I just got emailed this crash log from an internal app.
>
> Can anyone make head or tail of the cause? I'm no good with
> backtraces ...


> Error Log:
> Use of uninitialized value in concatenation (.) or string at /usr/ 
> share/perl5/DBD/SQLite.pm line 232.
> Use of uninitialized value in concatenation (.) or string at /usr/ 
> share/perl5/DBD/SQLite.pm line 232.
> Column 'AcctNoID' cannot be null at .client_services/forms/ 
> tab_form.pm line 5801.
> *** glibc detected *** perl: corrupted double-linked list:  
> 0x0b0d5b30 ***

The "glibc detected" message usually comes from inside malloc() when  
it detects heap corruption.  In fact, your backtrace agrees:


> ======= Backtrace: =========
> /lib/tls/i686/cmov/libc.so.6[0xb7e03d81]
> /lib/tls/i686/cmov/libc.so.6(__libc_malloc+0x8d)[0xb7e04cad]

Crash inside a malloc helper function...

> /usr/lib/libpixman-1.so.0[0xb77cd106]
> /usr/lib/libpixman-1.so.0(pixman_image_create_bits+0x3c)[0xb77cd62c]

called from inside pixman...

> /usr/lib/libcairo.so.2[0xb79bd941]
> /usr/lib/libcairo.so.2[0xb79f971c]
> /usr/lib/libcairo.so.2[0xb79f9b4e]
> /usr/lib/libcairo.so.2[0xb79caf16]
> /usr/lib/libcairo.so.2[0xb79cbcd4]
> /usr/lib/libcairo.so.2[0xb79cc0f2]
> /usr/lib/libcairo.so.2[0xb79cae39]
> /usr/lib/libcairo.so.2[0xb79cc8bc]
> /usr/lib/libcairo.so.2[0xb79cd0c0]
> /usr/lib/libcairo.so.2[0xb79cd83f]
> /usr/lib/libcairo.so.2[0xb79ca113]
> /usr/lib/libcairo.so.2[0xb79ba579]
> /usr/lib/libcairo.so.2(cairo_stroke_preserve+0x2c)[0xb79b2acc]
> /usr/lib/libcairo.so.2(cairo_stroke+0x12)[0xb79b2af2]

deep inside cairo...

> /usr/lib/gtk-2.0/2.10.0/engines/libaurora.so[0xb562d519]
> /usr/lib/gtk-2.0/2.10.0/engines/libaurora.so[0xb561e84c]

called by a theme engine from an expose handler.


But, since it's heap corruption, the actual location of the crash  
isn't really all that relevant.  This is where glibc stumbled across  
the broken heap structures, not when the problem actually occurred.   
Your first warning signs are the perl messages, first from SQLite and  
then from your app.  Clearly, there's an uninitialized value in use,  
and depending on what all that code does, that can result in strange  
things happening.


>

--
me, while driving the car: Okay, girls, what do you want for lunch?
yvonne: I wan' noo-tulls!
zella: I want lavaloli!  Can we go to the lavaloli store?
me: Um, where *is* the ravioli store?
zella: At the lavaloli store!
yvonne: I want noo-tulls!  Let's go to the noo-tull store!