GNOME Bugzilla – Bug 507579
crash in e_timezone_dialog_set_timezone (zone=0x0) at e-timezone-dialog.c:693
Last modified: 2008-01-07 18:31:24 UTC
What were you doing when the application crashed? Distribution: Unknown Gnome Release: 2.20.2 2007-12-15 (FreeBSD GNOME Project) BugBuddy Version: 2.20.1 System: FreeBSD 6.2-RELEASE-p7 FreeBSD 6.2-RELEASE-p7 #0: Mon Sep 3 21:26:24 PDT 2007 root@shuttle.paulbeard.org:/usr/obj/usr/src/sys/SHUTTLE i386 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 62004 vsize: 62004 resident: 28236 share: 59893707 rss: 28236 rss_rlim: 7059 CPU usage: start_time: 1199581224082632 rtime: 133 utime: 231 stime: 14151865 cutime:3620526 cstime: 1810263 timeout: 0 it_real_value: 0 frequency: 133 Backtrace was generated from '/usr/local/bin/evolution' (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 0x8223600 (LWP 100218)] [New Thread 0x806c000 (runnable)] [New LWP 100212] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Switching to LWP 100212] 0x2950a4f7 in pthread_testcancel () from /lib/libpthread.so.2
+ Trace 184221
Thread 3 (LWP 100212)
Thread 2 (Thread 0x806c000 (runnable))
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
I am running FreeBSD 6 and it's not clear to me (this early in the morning, anyway) how I enable a debug package to be built. There's no debug option in the "make config" dialog [hint or RFE, you choose]. If you can give me a nudge on how to do that, I'll send along the traces.
Apparently, compiling with WITH_DEBUG is useful. Does this help at all? I ran it under gdb and when it cored, I used bt to generate the following: Starting program: /usr/local/bin/evolution warning: Unable to get location for thread creation breakpoint: generic error [New LWP 100079] [New Thread 0x806f000 (LWP 100079)] CalDAV Eplugin starting up ... Loading Spamassasin as the default junk plugin ** (evolution:88052): DEBUG: mailto URL command: evolution %s ** (evolution:88052): DEBUG: mailto URL program: evolution Program received signal SIGSEGV, Segmentation fault.
+ Trace 184363
Thread 134672384 (LWP 100225)
that looks a lot better, can you also recompile evolution-data-server?
sure. how's this? Program received signal SIGSEGV, Segmentation fault.
+ Trace 184396
Thread 134672384 (LWP 100180)
beautiful trace, thanks a lot!
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 be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 492426 ***
you flatter me. it would be useful to make the process of generating a trace more accessible (making a standard config option or noting it somewhere). I realize this is more an issue for the porters/distros but it took me a bit of google-squeezing before I found it. In the end, I used make install WITH_DEBUG=1 FORCE_PKG_REGISTER=1 I don't know if DEBUG has any higher levels than 1: I assume it was a boolean ;-) Anyway, hope it helps.