Bug 587258 – Crash in message_removed() -- NULL hash table key

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 587258 - Crash in message_removed() -- NULL hash table key


Summary:	Crash in message_removed() -- NULL hash table key


Status:	RESOLVED DUPLICATE of bug 522277

Product:	Evolution Exchange
Classification:	Deprecated
Component:	Connector
Version:	2.24.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Connector Maintainer
QA Contact:	Ximian Connector QA

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-06-29 01:44 UTC by Matthew Barnes
Modified:	2009-06-29 04:04 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Matthew Barnes 2009-06-29 01:44:20 UTC

Forwarding from a Fedora bug:
http://bugzilla.redhat.com/show_bug.cgi?id=497974

Description of problem:
Since yesterday evolution-exchange crashes always while try getting folder
structure.

Version-Release number of selected component (if applicable):
evolution-exchange 2.24.5 1.fc10

How reproducible:

here it always happens on exchange contact. So evolution isn't usable anymore
for exchange server.

Steps to Reproduce:
1. starting evolution
2. contacting M$ exchange server

Actual results:
Crash

Expected results:
Should run

Additional info:
I have no idea whats happend and whats the difference to before where it
worked.

Comment 1 Matthew Barnes 2009-06-29 01:44:44 UTC

GDB Backtrace:

Starting program: /usr/libexec/evolution/2.24/evolution-exchange-storage 
[Thread debugging using libthread_db enabled]
[New Thread 0x7ffff7f947f0 (LWP 6540)]
[New Thread 0x7ffff2c2d950 (LWP 6546)]
[New Thread 0x7ffff2bec950 (LWP 6618)]
[New Thread 0x7ffff21eb950 (LWP 6635)]
[New Thread 0x7ffff17ea950 (LWP 6647)]
[New Thread 0x7ffff0de9950 (LWP 6648)]
[Thread 0x7ffff17ea950 (LWP 6647) exited]
[New Thread 0x7ffff17ea950 (LWP 6649)]
[New Thread 0x7fffebfff950 (LWP 6650)]
[Thread 0x7ffff17ea950 (LWP 6649) exited]
[Thread 0x7fffebfff950 (LWP 6650) exited]
[Thread 0x7ffff0de9950 (LWP 6648) exited]
[Thread 0x7ffff21eb950 (LWP 6635) exited]
[Thread 0x7ffff2bec950 (LWP 6618) exited]
[New Thread 0x7ffff2bec950 (LWP 6667)]
[Thread 0x7ffff2bec950 (LWP 6667) exited]
[New Thread 0x7ffff2bec950 (LWP 6668)]
[Thread 0x7ffff2bec950 (LWP 6668) exited]
[New Thread 0x7ffff2bec950 (LWP 6669)]

Program received signal SIGSEGV, Segmentation fault.
IA__g_str_hash (v=0x0) at gstring.c:95
95	  guint32 h = *p;

+ Trace 216239

#0 IA__g_str_hash
at gstring.c line 95
#1 g_hash_table_lookup_node
at ghash.c line 118
#2 IA__g_hash_table_lookup
at ghash.c line 668
#3 message_removed
at mail-stub-exchange.c line 405
#4 sync_deletions
at mail-stub-exchange.c line 1193
#5 connection_handler
at mail-stub.c line 168
#6 g_main_dispatch
at gmain.c line 2144
#7 IA__g_main_context_dispatch
at gmain.c line 2697
#8 g_main_context_iterate
at gmain.c line 2778
#9 IA__g_main_loop_run
at gmain.c line 2986
#10 bonobo_main
at bonobo-main.c line 311
#11 main
at main.c line 278


Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
Undefined command: "exit".  Try "help".
quit

Comment 2 Akhil Laddha 2009-06-29 04:04:46 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 522277 ***