[26059] in Athena Bugs
linux 9.3.12: Evolution
daemon@ATHENA.MIT.EDU (Bill Cattey)
Fri Sep 10 18:51:23 2004
Message-Id: <200409102251.i8AMpJKv030906@tokata.mit.edu>
To: bugs@mit.edu
Date: Fri, 10 Sep 2004 18:51:19 -0400
From: Bill Cattey <wdc@mit.edu>
Errors-To: bugs-bounces@mit.edu
System name: tokata.mit.edu
Type and version: i686 9.3.12 (with mkserv)
Display type: nVidia Corporation NV5 [RIVA TNT2/TNT2 Pro] (rev 15)
Shell: /bin/athena/tcsh
Window manager: sawfish
What were you trying to do?
Leave evolution running and do other stuff.
What's wrong:
It spontaneously core dumped.
What should have happened:
It should have stayed up.
Please describe any relevant documentation references:
I actually attached to the process and did a backtrace:
#0 0xb6544791 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#1 0xb6f7a4e4 in libgnomeui_segv_handle (signum=11) at gnome-ui-init.c:646
#2 0x0809b0ec in segv_redirect (sig=11) at main.c:500
#3 <signal handler called>
#4 0x08300c03 in ?? ()
#5 0xb712a045 in gdk_event_apply_filters (xevent=0xbfffc8b0, event=0x850fb88,
filters=0x846ca54) at gdkevents-x11.c:299
#6 0xb712aafa in gdk_event_translate (display=0x80c6290, event=0x850fb88,
xevent=0xbfffc8b0, return_exposes=0) at gdkevents-x11.c:814
#7 0xb712c589 in _gdk_events_queue (display=0x80c6290) at gdkevents-x11.c:1952
#8 0xb712c7cd in gdk_event_dispatch (source=0x80c7798, callback=0,
user_data=0x0) at gdkevents-x11.c:2012
#9 0xb6b397c0 in g_main_dispatch (context=0x80c77e0) at gmain.c:1653
#10 0xb6b3a827 in g_main_context_dispatch (context=0x80c77e0) at gmain.c:2197
#11 0xb6b3ac58 in g_main_context_iterate (context=0x80c77e0, block=1,
dispatch=1, self=0x80b71f8) at gmain.c:2278
#12 0xb6b3b49b in g_main_loop_run (loop=0x80d8c08) at gmain.c:2498
#13 0xb6dfa93a in bonobo_main () at bonobo-main.c:293
#14 0x0809b5e2 in main (argc=2, argv=0xbfffcc64) at main.c:637
If "gdk_event_apply_filters" means what I think it does, then I have
an idea what might have gone wrong.
At about the same time as the spontaneous core dump of Evolution, a message
came in from amb addressed to:
"various people who might be looking for me <amb@MIT.EDU>"
I have a presorting set of filters that examine incoming mail:
There are 3 rules, one matches a mailing list name,
the other two match on sender. I'm guessing that so long a sender
name blew out a buffer in the matching code, but I might be
totally wrong.
Any further speculation?
How can I help further examine this problem?
I tried to bounce the message back to myself and reproduce the failure, but
have as yet not seen neither the resend, nor the expected Evolution fault.
Oh well...
