[apport] gnome-system-log crashed with SIGSEGV in g_free()"

Bug #83883 reported by Chris Hofstaedtler
This bug report is a duplicate of:  Bug #69622: can't open gnome-system-log. Edit Remove
2
Affects Status Importance Assigned to Milestone
gnome-utils (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-utils

Just upgraded from edgy, applied all left-over updates. Tried opening the System Log Viewer from Control Panel, and before it came up, it already crashed.

ProblemType: Crash
Date: Wed Feb 7 23:36:55 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gnome-system-log
Package: gnome-utils 2.17.91-0ubuntu1
ProcCmdline: gnome-system-log
ProcCwd: /home/ch
ProcEnviron:
 LANGUAGE=de_AT:de
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=de_AT.UTF-8
 SHELL=/usr/bin/zsh
Signal: 11
SourcePackage: gnome-utils
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 g_free () from /usr/lib/libglib-2.0.so.0
Uname: Linux monique 2.6.20-6-generic #2 SMP Wed Jan 31 20:53:39 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
Chris Hofstaedtler (zeha) wrote :
Revision history for this message
Chris Hofstaedtler (zeha) wrote :

On subsequent runs, strace shows this as the last few lines:

open("/var/log/evms-engine.1.log", O_RDONLY|O_LARGEFILE) = 16
fadvise64_64(16, 0, 0, POSIX_FADV_SEQUENTIAL) = 0
fstat64(16, {st_mode=S_IFREG|0644, st_size=1139, ...}) = 0
fstat64(16, {st_mode=S_IFREG|0644, st_size=1139, ...}) = 0
read(16, "Feb 07 23:08:00 monique _5_ Engi"..., 1024) = 1024
close(16) = 0
open("/var/log/evms-engine.1.log", O_RDONLY|O_LARGEFILE) = 16
fadvise64_64(16, 0, 0, POSIX_FADV_SEQUENTIAL) = 0
fstat64(16, {st_mode=S_IFREG|0644, st_size=1139, ...}) = 0
read(16, "Feb 07 23:08:00 monique _5_ Engi"..., 8192) = 1139
read(16, "", 8192) = 0
close(16) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV (core dumped) +++
Process 26562 detached

Revision history for this message
Chris Hofstaedtler (zeha) wrote :

Installed some debug packages, gdb bt shows:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1225816384 (LWP 26872)]
string_get_date_string (line=0x49 <Address 0x49 out of bounds>) at logrtns.c:136
136 logrtns.c: No such file or directory.
 in logrtns.c
(gdb) bt
#0 string_get_date_string (line=0x49 <Address 0x49 out of bounds>) at logrtns.c:136
#1 0x080501c4 in log_read_dates (buffer_lines=0x8321360, current=1170886080) at logrtns.c:253
#2 0x08050479 in log_open (filename=0x8065768 "/var/log/evms-engine.1.log", show_error=0) at logrtns.c:422
#3 0x080529b2 in logview_add_logs_from_names (logview=0x809b800, lognames=0x805b708, selected=0x8066960 "/var/log/evms-engine.1.log")
    at logview.c:251
#4 0x0804db58 in main (argc=1, argv=0xbfca04a4) at main.c:179
#5 0xb7328ebc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#6 0x0804d7f1 in _start ()

hth,
-ch

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in gnome-utils:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.