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 353364 - crash in Evolution: Closing evolution.
crash in Evolution: Closing evolution.
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: general
2.8.x
Other All
: High critical
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-08-29 09:04 UTC by Mikael Nilsson
Modified: 2013-09-13 00:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
Trace (6.67 KB, text/plain)
2006-08-29 19:13 UTC, Mikael Nilsson
Details
New trace (6.05 KB, text/plain)
2006-08-29 21:14 UTC, Mikael Nilsson
Details
Another crash report (10.11 KB, text/plain)
2006-11-13 14:22 UTC, Mikael Nilsson
Details

Description Mikael Nilsson 2006-08-29 09:04:53 UTC
What were you doing when the application crashed?
Closing evolution.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.92 2006-08-22 (Ubuntu)
BugBuddy Version: 2.15.92

Memory status: size: 181665792 vsize: 0 resident: 181665792 share: 0 rss: 89714688 rss_rlim: 0
CPU usage: start_time: 1156835869 rtime: 0 utime: 4712 stime: 0 cutime:4013 cstime: 0 timeout: 699 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232681296 (LWP 5339)]
[New Thread -1302332512 (LWP 6928)]
[New Thread -1310860384 (LWP 5405)]
[New Thread -1292203104 (LWP 5386)]
[New Thread -1283748960 (LWP 5355)]
[New Thread -1266680928 (LWP 5353)]
[New Thread -1256985696 (LWP 5352)]
[New Thread -1248592992 (LWP 5351)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1232681296 (LWP 5339))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libc.so.6
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 es_menu_new
  • #4 <signal handler called>
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 ??
  • #31 ??
  • #32 ??
  • #33 ??
  • #34 ??
  • #35 ??
  • #36 ??
  • #37 ??
  • #38 ??
  • #39 ??
  • #40 ??
  • #41 ??
  • #0 __kernel_vsyscall

Comment 1 André Klapper 2006-08-29 10:35:37 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 Mikael Nilsson 2006-08-29 19:13:44 UTC
Created attachment 71855 [details]
Trace

With some debug packages. Do you need more?
Comment 3 André Klapper 2006-08-29 20:21:01 UTC
hmm, the evolution parts indeed are better now, but unfortunately not the crasher part which still only contains
  • #9 ??

Comment 4 Mikael Nilsson 2006-08-29 21:14:11 UTC
Created attachment 71869 [details]
New trace

Does this look better? Installed libc6-dbg too.
Comment 5 André Klapper 2006-11-09 23:53:23 UTC
sorry for coming back that late to you.

no, unfortunately that trace isn't better.
is this still an issue currently? perhaps this was a duplicate of bug 334966, which is fixed now?
Comment 6 Mikael Nilsson 2006-11-10 00:55:56 UTC
No, it's certainly not fixed.

The problem is that the backtrace is entirely different each time, so I guess this is a subtle overflow somewhere, that triggers different backtraces depending on memory layout or some such.

It's still 100% repeatable for me.

I'm now running Ubuntu edgy.

I'd be happy to rebuild the ubuntu package with any relevant modifications if that is a way to help trace this bug.

By the way, a collegue has the exact same crash, so I'm not alone.
Comment 7 André Klapper 2006-11-13 01:06:20 UTC
please install the dbg packages of evolution, evolution-data-server, gtkhtml, glib and gtk. thanks. :-)
Comment 8 Mikael Nilsson 2006-11-13 14:22:29 UTC
Created attachment 76485 [details]
Another crash report

With debug packages installed:

~$ dpkg -l libgtk2.0-0-dbg libglib2.0-0-dbg libgtkhtml3.8-dbg evolution-data-server-dbg evolution-dbg
Önskat=Okänd(U)/Installera(I)/Radera(R)/Rensa(P)/Håll(H)
| Status=Ej(N)/Installerad(I)/Konf.(C)/Uppackad(U)/Misslyckad(F)/Delvis(H)
|/ Fel?Inget(=)/Håll(H)/Ominstallera(R)/Båda(X) (Status,Fel: versaler=illa)
||/ Namn                            Version                         Beskrivning
+++-===============================-===============================-==============================================================================
ii  evolution-data-server-dbg       1.8.1-0ubuntu3                  evolution database backend server with debugging symbols
ii  evolution-dbg                   2.8.1-0ubuntu4                  The groupware suite - with debugging symbols
ii  libglib2.0-0-dbg                2.12.4-0ubuntu1                 The GLib libraries and debugging symbols
ii  libgtk2.0-0-dbg                 2.10.6-0ubuntu1                 The GTK+ libraries and debugging symbols
ii  libgtkhtml3.8-dbg               3.12.1-0ubuntu1                 HTML rendering/editing library - debug files

(only gtkhtml was missing earlier)
Comment 9 André Klapper 2006-11-13 14:30:46 UTC
strange, the stacktrace is still not useful.
i have no idea how to deal with this here, sorry - perhaps a developer has an idea?
Comment 10 Mikael Nilsson 2006-11-13 16:26:25 UTC
Note that the backtrace begins with

  • #41 ??

which is NULL - cannot be a correct address...
Comment 11 Tobias Mueller 2008-02-29 21:02:21 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!