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 380410 - crash in System Log: I did nothing. Had it r...
crash in System Log: I did nothing. Had it r...
Status: RESOLVED FIXED
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: 2006-11-29 08:23 UTC by Alf-Ivar/Affi Holm
Modified: 2007-02-26 19:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Alf-Ivar/Affi Holm 2006-11-29 08:23:32 UTC 
Version: 2.16.1

What were you doing when the application crashed?
I did nothing.  Had it running when I went home.  

I can't see from the details when it happened, but since it is a log viewing tool, I would look into log rotation.


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

Memory status: size: 32600064 vsize: 0 resident: 32600064 share: 0 rss: 14888960 rss_rlim: 0
CPU usage: start_time: 1164703765 rtime: 0 utime: 1300 stime: 0 cutime:1282 cstime: 0 timeout: 18 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 -1225054016 (LWP 32274)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 90207

Thread 1 (Thread -1225054016 (LWP 32274))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strrchr
    from /lib/tls/i686/cmov/libc.so.6
  • #5 ??
  • #6 ??
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2006-11-29 13:35:16 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


Alf-Ivar/Affi Holm





          2006-11-30 08:31:18 UTC
        



Installed various -dbgsym packages, and went home.  Another crash tonight.  This is the details I got today.  If I should install more -dbgsym packages, please tell me which!

- Affi

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

Memory status: size: 33439744 vsize: 0 resident: 33439744 share: 0 rss: 15933440 rss_rlim: 0
CPU usage: start_time: 1164808995 rtime: 0 utime: 1107 stime: 0 cutime:1073 cstime: 0 timeout: 34 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 -1224804160 (LWP 17064)]
0xffffe410 in __kernel_vsyscall ()




+
Trace
    90494






Thread 1
          (Thread -1224804160 (LWP 17064))


    

  • 
#0
__kernel_vsyscall

    • 

  • 
#1
__waitpid_nocancel

    
                from
                /lib/tls/i686/cmov/libpthread.so.0

    

    • 

  • 
#2
gnome_gtk_module_info_get

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

    

    • 

  • 
#3
<signal handler called>

    • 

  • 
#4
strrchr

    
                from
                /lib/tls/i686/cmov/libc.so.6

    

    • 

  • 
#5
logview_repaint

    
                at log_repaint.c
                  line
                  186

    

    • 

  • 
#6
gnome_vfs_monitor_callback

    
                from
                /usr/lib/libgnomevfs-2.so.0

    

    • 

  • 
#7
g_idle_dispatch

    
                at gmain.c
                  line
                  3926

    

    • 

  • 
#8
IA__g_main_context_dispatch

    
                at gmain.c
                  line
                  2045

    

    • 

  • 
#9
g_main_context_iterate

    
                at gmain.c
                  line
                  2677

    

    • 

  • 
#10
IA__g_main_loop_run

    
                at gmain.c
                  line
                  2881

    

    • 

  • 
#11
IA__gtk_main

    
                at gtkmain.c
                  line
                  1024

    

    • 

  • 
#12
main

    
                at main.c
                  line
                  203

    

    • 

  • 
#13
__libc_start_main

    
                from
                /lib/tls/i686/cmov/libc.so.6

    

    • 

  • 
#14
_start

    • 

  • 
#0
__kernel_vsyscall

    • 













Comment 3


Emmanuele Bassi (:ebassi)





          2006-11-30 10:05:42 UTC
        



thanks for the stack trace.

fixed in HEAD.

2006-11-30  Emmanuele Bassi  <ebassi@cvs.gnome.org>

        * log_repaint.c: Check the return value of strrchr(). (should
        fix #380410 and duplicates)






Comment 4


André Klapper





          2007-02-26 19:36:08 UTC
        



fix in CVS HEAD/SVN trunk:
http://svn.gnome.org/viewcvs/gnome-utils/trunk/logview/log_repaint.c?r1=6916&r2=7282

backported to gnome-2-16 branch at 2007-01-13:
http://svn.gnome.org/viewcvs/gnome-utils/branches/gnome-2-16/logview/log_repaint.c?r1=7152&r2=7331

according to http://bugzilla.gnome.org/show_bug.cgi?id=355887#c120 this will probably also fix bug 355887 with 164 duplicates.