GNOME Bugzilla – Bug 545517
gnome-extra/evolution-exchange-2.22.0: SIGSEV in e2k-restriction.c
Last modified: 2008-08-05 05:15:47 UTC
Steps to reproduce: You need to install the IM Pidgin. I am using version 2.4.3. 1. evolution --force-shutdown 2. pidgin 3. enable Evolution Integration plugin 4. double-click onto a contact Stack trace:
+ Trace 204181
Thread 3 (Thread 0x40953950 (LWP 31099))
495 in e2k-restriction.c Other information: This bug has been reported in gentoo's bugzilla as well. See bug #233263 for more details. https://bugs.gentoo.org/show_bug.cgi?id=233263 BR, Dustin
can you please provide full traces with crash point. Current trace doesn't have <signal_handler> or <segv> call.
Could you give me a hint how to do this?
General guidelines - http://live.gnome.org/GettingTraces If you running application in gdb, please see http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running
I've rebuild evolution-data-server, evolution-exchange and evolution to provide debug information and tried to obtain a more useful backtrace following the documentation you provided in comment #3. But I cannot find< signal_handler> or <segv> calls in either 'thread apply all bt' of '/usr/libexec/evolution/2.22/evolution-exchange-storage', '/usr/libexec/evolution-data-server-2.22' or '/usr/bin/pidgin'. Any idea how to proceed?
Sorry for confusion. < signal_handler> or <segv> calls come in bug buddy traces which indicate where application has crashed. But when we run in gdb, it has given crash point already and after getting crash point, we do 't a a bt'. For example traces will look like Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb34fbb90 (LWP 4182)] 0xb6133450 in ?? () from /lib/libc.so.6 (gdb) t a a bt
+ Trace 204263
Thread 72 (Thread 0xb34fbb90 (LWP 4182))
and continue ..... And if you can provide traces of /usr/libexec/evolution/2.22/evolution-exchange-storage as well as /usr/bin/evolution process, it would be really helpful.
Okay. I already provided a backtrace of evolution-exchange-2.22.0 in when I opened the bug. I've upgrade to evolution-exchange-2.22.3 in the meantime as I was requested in the gentoo bug. Here is the traceback of this version: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x415f7950 (LWP 17588)] e2k_restriction_unref (rn=0x0) at e2k-restriction.c:495 495 e2k-restriction.c: No such file or directory. in e2k-restriction.c (gdb) t a a bt
+ Trace 204264
Thread 4 (Thread 0x415f7950 (LWP 17588))
I am not accessing evolution-exchange via evolution but via pidgin. I can provide a backtrace from that program as well if required. Furthermore I repost some information from the gentoo bug: Additionally, I've found the following: If you have configured a Global Address List in an Exchange account, you can observe the following behavior: 1) You have started evolution and authenticated to the GAL server in evolution by accessing the address book and provided your login credentials (either saved or entered in the pop-up dialog) and then double-click onto a contact in pidgin (using the Evolution Integration plugin), pidgin behaves correctly. 2) You have started evolution but have NOT authenticated to the GAL server in evolution and then double-click onto a contact in pidgin (using the Evolution Integration plugin), pidgin freezes waiting for a response and evolution-exchange segfaults. 3) You have not started evolution and Not authenticated to the GAL server, then double-click onto a contact in pigdin (using the Evolution Integration plugin), same result as 2).
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 473924 ***