On Sun, 2004-02-29 at 17:55, Philipp Grosswiler wrote: > OK, now I got something for you... but could be that the problem is already > solved in the latest CVS version... just that the latest CVS is not working > for me (see my earlier post about readdb()). >
> (gdb) continue > Continuing. > [New Thread 278546 (LWP 6642)] > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 32769 (LWP 6269)] > 0x4009511b in pthread_start_thread_event () from /lib/i686/libpthread.so.0 > (gdb) bt > #0 0x4009511b in pthread_start_thread_event () from > /lib/i686/libpthread.so.0 > #1 0x43000000 in ?? () > #2 0x00000f21 in ?? () > #3 0x08b90ca0 in ?? () > #4 0x08053458 in ?? () > #5 0x0805345c in ?? () > #6 0x08053460 in ?? () > #7 0x08053464 in ?? () > #8 0x08053474 in ?? () > #9 0x4000d290 in _dl_runtime_resolve () from /lib/ld-linux.so.2 > #10 0x42e01000 in ?? () > #11 0x42e00000 in ?? () > #12 0x00001000 in ?? () > #13 0x001ff000 in ?? () > #14 0x4009d68c in __JCR_LIST__ () from /lib/i686/libpthread.so.0 > #15 0x08050660 in ?? () > #16 0x00000006 in ?? () > #17 0x08053604 in ?? () > #18 0x40094ccf in __pthread_manager () from /lib/i686/libpthread.so.0 The libpthread thread manager seg faulted. I've never seen that happen before. I guess that would be either a bug in libpthread or some very bad memory corruption somewhere. A quick Google doesn't come up with any one else seeing this particular crash. I'll have to ask some people. Cheers. -trog
signature.asc
Description: This is a digitally signed message part
