GNOME Bugzilla – Bug 223446
The gnome-gtkhtml-editor crashes when trying to reply to a message
Last modified: 2002-07-29 19:22:51 UTC
Package: Evolution Priority: Normal Version: 1.0.2 Synopsis: The gnome-gtkhtml-editor crashes when trying to reply to a message Bugzilla-Product: Evolution Bugzilla-Component: Mailer Description: I got some spam about digital web books and when I tried to reply to be removed, the gnome-gtkhtml-editor kept crashing. Once this bug is opened, I'll include the problematic message. Debugging Information: (no debugging symbols found)...0x40cf11d9 in __wait4 () from /lib/i686/libc.so.6
+ Trace 20863
Created attachment 41152 [details] Problematic Mail Message
I'm using evolution-1.0.3-ximian.4 as delivered by Red Carpet. I don't know how Bug Buddy came up with 1.0.2.
Not your fault, but the the trace is useless.
Does this help? I had evo running, I did the gdb and ran the editor, and then replied in evo to cause the crash again: wintermute> gdb gnome-gtkhtml-editor GNU gdb Red Hat Linux (5.1-1) Copyright 2001 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"... (no debugging symbols found)... (gdb) run Starting program: /usr/bin/gnome-gtkhtml-editor gtkhtml-WARNING **: Getting cursor base for an HTMLText with no slaves -- 0x81011c8 gtkhtml-WARNING **: Getting cursor base for an HTMLText with no slaves -- 0x81011c8 gtkhtml-CRITICAL **: file htmlclueflow.c: line 2841 (html_clueflow_is_empty): assertion `HTML_IS_CLUEFLOW (flow)' failed. Program received signal SIGSEGV, Segmentation fault. 0x00000000 in ?? () ((gdb) where
+ Trace 20866
ok, it looks like a real bug. please could you attach this message to this bugreport?
s/this message/crashing message ;-)
I already did (id=1615)...
*** bug 225787 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 224322 ***
fixed in CVS
resolve as fixed