GNOME Bugzilla – Bug 522368
Evo crashes in groupwise_folder_item_to_msg at camel-groupwise-folder.c:1694 on specific message
Last modified: 2008-09-17 17:28:46 UTC
I am using Ubuntu 8.04 (Hardy) 64 bit distribution. I found that using Evolution with GW connector crashes with the specific messages. I am also using Evolution on Ubuntu 7.10 32 bit without any problem. Can you fix the crashes? Attaching logs. Thank you in advance! KAMI
Created attachment 107275 [details] Evo log
Created attachment 107276 [details] Evo gdb log
Created attachment 107277 [details] Evo gdb - thread log
Hi :) Thanks for that bugreport. Could you get us a stacktrace with debug symbols please? Especially for Evolution and Evolution-data-server. Can you attach the message (with full headers and stuff) as well?
Can you be so kind to write how can I do it. Then I will do it on Monday.
You might have luck on http://live.gnome.org/GettingTraces and following pages such as http://live.gnome.org/GettingTraces/DistroSpecificInstructions#head-46c81b990ba060e2668c48d93ddb541e57dc6291. For the specific message: Select the message with the non-crashing-evo and click View-Sources or the like. Please attach that here.
Created attachment 107435 [details] gdb with debug packages #1
Created attachment 107436 [details] gdb with debug packages #2 Added traces with debub packages installed.
Created attachment 107437 [details] gdb with debug packages #3 (another message)
Created attachment 107439 [details] the message: gdb with debug packages #3 (another message) Attached the message. Note this one comes from web interface of Groupwise, because I didn't find option in the real GW client, and I haven't got non crashing Evolution client this time. Do you need more information?
Stacktrace from comment #8:
+ Trace 192685
Thread 13 (Thread 0x413e6950 (LWP 18717))
Thanks for providing the information. I'll set the bug to NEW; let's hope, a e-d-s developer comes across this bug.
Created attachment 118891 [details] [review] proposed eds patch for evolution-data-server; This is only blind patch, based on traces. I do not have GW, thus would be great if someone can test this or something.
Oops, forget that. Tobias found the bug with proper fix in bug #519537. Thus obsoleting my patch and marking as this bug as duplicate. *** This bug has been marked as a duplicate of 522389 ***