On 08 Jun 2001 15:03:03 -0700, Jon Nall wrote:
>
> i'm still trying to figure out exactly how to make wombat crash
> reproducibly. (and how to fix it). i have a stack trace from the wombat
> crash below. i'm sorry to bug people if this has been fixed in the
> snapshots, but as it says below, i'm on a PPC machine, so i'm just using
> the preview rpm.
>
> thanks.
> nall.
>
> (no debugging symbols found)...0xefb4a00 in wait4 () at soinit.c:59
> #0 0xefb4a00 in wait4 () at soinit.c:59
> #1 0xefb49b4 in waitpid () at ../sysdeps/unix/sysv/linux/waitpid.c:26
> #2 0xf476cc0 in waitpid () at wrapsyscall.c:105
> #3 0xfc53878 in gnome_segv_handle (signum=11) at gnome-init.c:659
> #4 0xf474e50 in pthread_sighandler (signo=11, ctx=0x7fffef90) at
> signals.c:96
> #5 <signal handler called>
> #6 0xef8f454 in strlen () at soinit.c:59
> #7 0x1000d504 in pas_book_factory_get_type ()
> #8 0x1002f4b0 in e_list_append ()
> #9 0x1000f138 in pas_book_factory_get_type ()
> #10 0x1000f7dc in pas_book_factory_get_type ()
> #11 0xf87e57c in gtk_marshal_NONE__NONE () at gtkmarshal.c:124
This looks like your stack is getting crushed. If you can figure out
how to reproduce this we can try it on our purify box.
Thanks,
Chris
_______________________________________________
evolution maillist - [EMAIL PROTECTED]
http://lists.helixcode.com/mailman/listinfo/evolution
