GNOME Bugzilla – Bug 417120
crash in System Log: VWvare - windows XP inst...
Last modified: 2007-03-12 10:25:07 UTC
Version: 2.16.1 What were you doing when the application crashed? VWvare - windows XP install Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 38289408 vsize: 0 resident: 38289408 share: 0 rss: 17027072 rss_rlim: 0 CPU usage: start_time: 1173628743 rtime: 0 utime: 132 stime: 0 cutime:125 cstime: 0 timeout: 7 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-system-log' (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 -1225148224 (LWP 4985)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 117727
Thread 1 (Thread -1225148224 (LWP 4985))
Thanks for taking the time to report this bug. Unfortunately, that 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
The rapport is a bit inaccurate I was doing a "find" operation in the log viewer, the program then crashed as I deleted and added chars in the search. I will try to reproduce the error.
Looks like I managed to do it again: and filed another bug rapport; 417271. What were you doing when the application crashed? Using the filter funktion Typing chars and deleting them again Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 43556864 vsize: 0 resident: 43556864 share: 0 rss: 20779008 rss_rlim: 0 CPU usage: start_time: 1173653571 rtime: 0 utime: 308 stime: 0 cutime:299 cstime: 0 timeout: 9 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-system-log' (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 -1224877888 (LWP 14417)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 117846
Thread 1 (Thread -1224877888 (LWP 14417))
(In reply to comment #3) > Looks like I managed to do it again: > and filed another bug rapport; 417271. That's actually a different report (and a duplicate of another bug, as now noted on that report). How to tell they're different problems: 1st stacktrace > #3 <signal handler called> > #4 0xb7399a09 in free () from /lib/tls/i686/cmov/libc.so.6 > #5 0xb74adb51 in g_free () from /usr/lib/libglib-2.0.so.0 > #6 0xb7a0bcf9 in gtk_tree_path_free () from /usr/lib/libgtk-x11-2.0.so.0 2nd stacktrace > #3 <signal handler called> > #4 0xb7a5b951 in gtk_tree_sortable_sort_column_changed () > from /usr/lib/libgtk-x11-2.0.so.0 > #5 0xb7a4f70a in gtk_tree_model_get_iter () from /usr/lib/libgtk-x11-2.0.so.0 > #6 0xb7a4f839 in gtk_tree_row_reference_new_proxy () > from /usr/lib/libgtk-x11-2.0.so.0 > #7 0xb7a69c36 in gtk_tree_view_scroll_to_cell () > from /usr/lib/libgtk-x11-2.0.so.0 Note the completely different function calls after the <signal handler changed> line. The first report is still a problem, and we don't yet have debug symbols for it. If you can reproduce the first problem, then can you go to http://live.gnome.org/GettingTraces, install the debug symbols for glib and gtk, and then get us a new stack trace. Thanks!
This is better no? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 61857792 vsize: 0 resident: 61857792 share: 0 rss: 38993920 rss_rlim: 0 CPU usage: start_time: 1173655473 rtime: 0 utime: 542 stime: 0 cutime:528 cstime: 0 timeout: 14 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-system-log' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225570112 (LWP 6134)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 117861
Thread 1 (Thread -1225570112 (LWP 6134))
(In reply to comment #5) > This is better no? It's a bit better, and we can now find out that this is a duplicate of Bug 369170 (which also needs more information). > #3 <signal handler called> > #4 0xffffe410 in __kernel_vsyscall () > #5 0xb72f5770 in raise () from /lib/tls/i686/cmov/libc.so.6 > #6 0xb72f6ef3 in abort () from /lib/tls/i686/cmov/libc.so.6 > #7 0xb732ad0b in __fsetlocking () from /lib/tls/i686/cmov/libc.so.6 > #8 0xb7332b4a in free () from /lib/tls/i686/cmov/libc.so.6 > #9 0xb7446b51 in IA__g_free (mem=0x99a2c90) at gmem.c:187 > #10 0xb79a4cf9 in IA__gtk_tree_path_free (path=0x83ab7f0) > at gtktreemodel.c:632 > #11 0x08052a3a in ?? () > #12 0x083ab7f0 in ?? () > #13 0xbf81a63c in ?? () > #14 0xbf81a608 in ?? () > #15 0xb79a70dd in IA__gtk_tree_model_get (tree_model=0x823e8a0, iter=0x19) > at gtktreemodel.c:1401 > #16 0x080549b1 in ?? () > #17 0x080a2800 in ?? () > #18 0x0851e0f0 in ?? () > #19 0x00000000 in ?? () Thanks for the extra gtk symbols, but the series of "??" lines are still a problem. They can probably be resolved by adding the debug symbols for gnome-utils as well. Can you please direct any new comments onto Bug 369170 so we can get the information to the other people with the same bug? Thanks! *** This bug has been marked as a duplicate of 369170 ***