[Gllug] exim segfault puzzle

[Nix]

On 22 Dec 2007, Richard Jones told this:
> It always segfaults when delivering the same mail: an automatically

That alone screams `not a hardware problem'. They're invariably
intermittent segfaults in wildly divergent places.

> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1078686048 (LWP 23605)]
> 0x400ec4f2 in __ham_copy_item () from /usr/lib/libdb3.so.3
> (gdb) bt
> #0  0x400ec4f2 in __ham_copy_item () from /usr/lib/libdb3.so.3
> #1  0x400ebb37 in __ham_split_page () from /usr/lib/libdb3.so.3
> #2  0x400e06f9 in __ham_c_dup () from /usr/lib/libdb3.so.3
> #3  0x400e02e3 in __ham_c_dup () from /usr/lib/libdb3.so.3
> #4  0x400c2e77 in __db_c_put () from /usr/lib/libdb3.so.3
> #5  0x400beb55 in __db_put () from /usr/lib/libdb3.so.3
> #6  0x08052101 in ?? ()
> #7  0x080ca748 in ?? ()
> #8  0x00000000 in ?? ()

Bug in ancient version of libdb? (It could equally be an attempt to put
a null pointer into the db, and thus a bug in exim: the fact that the
crash is happening inside __ham_copy_item() strongly suggests that.)

I'd recommend recompiling exim with debugging symbols and/or getting the
debugging symbol package. With a proper backtrace this is probably
fixable.


-- 
`The rest is a tale of post and counter-post.' --- Ian Rawlings
                                                   describes USENET
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug