GNOME Bugzilla – Bug 543336
Opening a Task crashed Evolution
Last modified: 2008-10-01 15:48:27 UTC
Steps to reproduce: 1. Converted a mail into a task 2. Try to open the new task for modification 3. Stack trace:
+ Trace 203017
Thread 1 (Thread 0xb65a0740 (LWP 11999))
Other information: The task has 14 attachments, weighing 7~8MB in total. With another task and attachments for less than 1MB it works fine.
which is the evolution version 2.22.x ? trace doesn't contain <signal_handler> or <segv> call, can you please provide full traces and please install gtk2, glib2 debuginfo rpms also, thanks in advance.
Sorry for the version, picked up the wrong number from the list, changed now in 2.22.x. Exact version is 2.22.2. Going to provide a new stack trace.
Created attachment 114725 [details] New stack trace Attached the stack trace instead of pasting it into message body, hope it's not wrong...
Milo, are you providing traces using gdb or bug-buddy ? If you are using gdb, then please provide traces above the crash so that it will help us in identifying the crash point. Like start evolution in gdb , when it crashes do 't a a bt' and paste traces below this command as well as little bit above it also.
(In reply to comment #4) > Milo, are you providing traces using gdb or bug-buddy ? If you are using gdb, > then please provide traces above the crash so that it will help us in > identifying the crash point. Like start evolution in gdb , when it crashes do > 't a a bt' and paste traces below this command as well as little bit above it > also. I'm using gdb for the traces. Actually, what I attached here is the output below "thread apply all bt" after the crash. I will paste also something above that point too (not before tonight GMT+1 though). If I have to do something different, please tell me, I'm not an expert of gdb...
see bug 543388 for reference. I am looking for trace like , Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb644f6e0 (LWP 25052)] 0xb7d9fbdd in summary_build_content_info (s=0x8115018, msginfo=0x83250c8, mp=0x8277d00) at camel-folder-summary.c:3213 3213 while (calendar_header [calendar_header_offset] && isspace (calendar_header [calendar_header_offset])) (gdb) thread a a bt
+ Trace 203147
Thread 1 (Thread 0xb644f6e0 (LWP 25052))
And besides 'thread a a bt' please do 'bt full' also so that it will give values of function during crash. I hope i am clear.
Created attachment 114781 [details] New stack trace This is the new trace, I copied everything from the start of the program to the end of "thread a a bt".
Created attachment 114782 [details] Output of "bt full" This is the output of "bt full".
Thanks Milo for good traces.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should work fine with 2.22.3.1 or even better with 2.24.0. *** This bug has been marked as a duplicate of 460204 ***