GNOME Bugzilla – Bug 398824
crash in Archive Manager: Opened a lha-archiv crea...
Last modified: 2007-06-04 15:12:39 UTC
Version: 2.16.1 What were you doing when the application crashed? Opened a lha-archiv created with an Amiga ( has amiga-specific file-flags ). FileRoller opened and crashed. Program "lha" can deal with the archive, I suspect this program is used by Fileroller? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 52105216 vsize: 0 resident: 52105216 share: 0 rss: 13455360 rss_rlim: 0 CPU usage: start_time: 1169323697 rtime: 0 utime: 36 stime: 0 cutime:34 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/file-roller' (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 -1224968000 (LWP 6567)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 103855
Thread 1 (Thread -1224968000 (LWP 6567))
Created attachment 80772 [details] Archiv that triggers crash
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!
I hoped the bug would be reproduceable with the archive I attached. Wouldnt the preferable way be to trace the bug on your own system ? (Besides that the symbols dint add a great deal of detail) Besides, the info at the link is wrong, debug-symbols-packages in Ubuntu Edgy have -dbg at the end. Stacktrace with symbols installed following... Have fun!
Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 52101120 vsize: 0 resident: 52101120 share: 0 rss: 13418496 rss_rlim: 0 CPU usage: start_time: 1169332902 rtime: 0 utime: 36 stime: 0 cutime:33 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/file-roller' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1224947520 (LWP 5678)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 103896
Thread 1 (Thread -1224947520 (LWP 5678))
I reproduce the bug with 2 different versions of fileroller under valgrind with the archive you provide. It happens all the time, it should be easy to fix. Mark it has Verified. beta@elmarco-laptop:~$ file-roller --version GNOME file-roller 2.16.1 I can reproduce the crash. beta@elmarco-laptop:~$ /opt/gnome2/bin/file-roller --version GNOME file-roller 2.17.90 I can reproduce the crash. ==8374== Invalid read of size 1 ==8374== at 0x402205A: index (mc_replace_strmem.c:163) ==8374== by 0x8068DB2: process_line (fr-command-lha.c:69) ==8374== by 0x806FA66: process_output (fr-process.c:499) ==8374== by 0x806FAEE: check_child (fr-process.c:716) ==8374== by 0x4E9B025: g_timeout_dispatch (gmain.c:3422) ==8374== by 0x4E9AA51: g_main_context_dispatch (gmain.c:2045) ==8374== by 0x4E9DA2E: g_main_context_iterate (gmain.c:2677) ==8374== by 0x4E9DDD8: g_main_loop_run (gmain.c:2881) ==8374== by 0x4788103: gtk_main (gtkmain.c:1148) ==8374== by 0x8075FBF: main (main.c:238) ==8374== Address 0x0 is not stack'd, malloc'd or (recently) free'd
Created attachment 82425 [details] [review] add [unknown] support and minor pointer check stuff
*** Bug 421195 has been marked as a duplicate of this bug. ***
Ping ping? Can someone review the patch?
*** Bug 431102 has been marked as a duplicate of this bug. ***
Marc-Andre, your patch looks good, I've applied it to current SVN. Thanks.