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 422773 - crash in System Log: I just started this app ...
crash in System Log: I just started this app ...
Status: RESOLVED DUPLICATE of bug 364106
Product: gnome-utils
Classification: Deprecated
Component: logview
2.16.x
Other All
: High critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-25 20:41 UTC by janusz.krupski
Modified: 2007-04-07 14:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description janusz.krupski 2007-03-25 20:41:13 UTC 
Version: 2.16.1

What were you doing when the application crashed?
I just started this app and it crashes.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 151236608 vsize: 151236608 resident: 14848000 share: 9986048 rss: 14848000 rss_rlim: -1
CPU usage: start_time: 1174855240 rtime: 28 utime: 25 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-system-log'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47615542437104 (LWP 8807)]
(no debugging symbols found)
0x00002b4e59695eb5 in waitpid () from /lib/libpthread.so.0

+ Trace 122179

Thread 1 (Thread 47615542437104 (LWP 8807))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 __libc_start_main
    from /lib/libc.so.6
  • #9 ??
  • #10 ??
  • #11 ??
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


Damien Durand





          2007-03-26 19:48:42 UTC
        



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!







Comment 2


janusz.krupski





          2007-03-26 20:33:02 UTC
        



(In reply to comment #1)
> 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!
> 

Hello again,

Thanks for info how to install packages with dbgsyms. Now I can post better stack trace. I hope this log is enough to know what was wrong with this application.

Regards.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 151228416 vsize: 151228416 resident: 14843904 share: 9986048 rss: 14843904 rss_rlim: -1
CPU usage: start_time: 1174939712 rtime: 45 utime: 38 stime: 7 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-system-log'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 48001676584176 (LWP 7901)]
0x00002ba840ccdeb5 in waitpid () from /lib/libpthread.so.0




+
Trace
    122417






Thread 1
          (Thread 48001676584176 (LWP 7901))


    

  • 
#0
waitpid

    
                from
                /lib/libpthread.so.0

    

    • 

  • 
#1
gnome_gtk_module_info_get

    
                from
                /usr/lib64/libgnomeui-2.so.0

    

    • 

  • 
#2
<signal handler called>

    • 

  • 
#3
string_get_date_string

    
                at logrtns.c
                  line
                  136

    

    • 

  • 
#4
log_read_dates

    
                at logrtns.c
                  line
                  253

    

    • 

  • 
#5
log_open

    
                at logrtns.c
                  line
                  422

    

    • 

  • 
#6
logview_add_logs_from_names

    
                at logview.c
                  line
                  251

    

    • 

  • 
#7
main

    
                at main.c
                  line
                  179

    

    • 

  • 
#8
__libc_start_main

    
                from
                /lib/libc.so.6

    

    • 

  • 
#9
_start

    • 

  • 
#0
waitpid

    
                from
                /lib/libpthread.so.0

    

    • 









... and another log from gdb:


snake@developer:~$ gdb gnome-system-log 
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/gnome-system-log 
[Thread debugging using libthread_db enabled]
[New Thread 47805232174320 (LWP 8038)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47805232174320 (LWP 8038)]
string_get_date_string (line=0x41 <Address 0x41 out of bounds>) at logrtns.c:136
136     logrtns.c: No such file or directory.
        in logrtns.c
(gdb)







Comment 3


palfrey





          2007-04-07 14:06:05 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 364106 ***