GNOME Bugzilla – Bug 170244
gnome-system-log crashes when viewing /var/log/syslog (monitorer)
Last modified: 2006-07-03 14:54:26 UTC
Distribution: Debian 3.1 Package: gnome-utils Severity: normal Version: GNOME2.10.0 2.10.0 Gnome-Distributor: Ubuntu Synopsis: gnome-system-log crashes when viewing /var/log/syslog (monitorer) Bugzilla-Product: gnome-utils Bugzilla-Component: logview Bugzilla-Version: 2.10.0 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Summary says it all Steps to reproduce the crash: 1. use application to open /var/log/syslog 2. select the option to "monitor". 3. Expected Results: It crashes. How often does this happen? 2nd time in a row now, so currently always. Additional Information: Debugging Information: 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) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1221545152 (LWP 1535)] (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 56823
Thread 1 (Thread -1221545152 (LWP 1535))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-13 17:37 ------- Unknown version 2.10.0 in product gnome-utils. Setting version to "2.10.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-utils". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was rebroad@gmail.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces.
*** Bug 171616 has been marked as a duplicate of this bug. ***
*** Bug 300374 has been marked as a duplicate of this bug. ***
Created attachment 45902 [details] [review] Path to fix segfault Looks like ReadNewLines or ReadLastPage sometimes return NULL instead of a table. So this small fix prevents a segfault if this is the case.
I have applied your patch, please note that things are very unstable right now in CVS (file monitoring does not work just yet). Thanks !
*** Bug 307999 has been marked as a duplicate of this bug. ***
*** Bug 308009 has been marked as a duplicate of this bug. ***
*** Bug 310646 has been marked as a duplicate of this bug. ***
This issue should be fixed in cvs HEAD. Could you please try out the cvs version of gnome-system-log, and see if it fixes the problem ? If you don't have access to cvs, please try the 2.13.1 version, which should be out on october 24th, and report back. Thanks for your help !
Assume it was fixed. All dupes are from older versions. Please reopen if it was not.