GNOME Bugzilla – Bug 369170
crash in System Log: I was working on log vis...
Last modified: 2008-12-23 14:28:15 UTC
Version: 2.16.1 What were you doing when the application crashed? I was working on log visualizing Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 69537792 vsize: 0 resident: 69537792 share: 0 rss: 28426240 rss_rlim: 0 CPU usage: start_time: 1162428796 rtime: 0 utime: 895 stime: 0 cutime:889 cstime: 0 timeout: 6 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 -1225385792 (LWP 4578)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 81692
Thread 1 (Thread -1225385792 (LWP 4578))
*** Bug 376785 has been marked as a duplicate of this bug. ***
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!
*** Bug 401519 has been marked as a duplicate of this bug. ***
*** Bug 404572 has been marked as a duplicate of this bug. ***
*** Bug 417120 has been marked as a duplicate of this bug. ***
Hi all I was asked to post here and not in bug 417120 To reproduce this crash: Use filter utility and add chars and remove chars... at some point I click on the clear button and the program crash. I also think you can reproduce by just adding or removing chars, however I am not sure. If you need more symbols let me know which plz. // Daniel Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 47697920 vsize: 0 resident: 47697920 share: 0 rss: 24932352 rss_rlim: 0 CPU usage: start_time: 1173716295 rtime: 0 utime: 326 stime: 0 cutime:318 cstime: 0 timeout: 8 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-system-log' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225459520 (LWP 5734)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 118021
Thread 1 (Thread -1225459520 (LWP 5734))
Ubuntu bug about that on GNOME 2.18: https://launchpad.net/bugs/92575
A decent stack trace. Confirming.
Logview has been rewritten, so this is OBSOLETE now.