! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
Crash while opening tar.bz2 archive
Status:
RESOLVED: FIXED
Severity:
critical
Product:
Xarchiver
Component:
general

Comments

Description Christoph Wickert editbugs 2008-10-28 22:12:41 CET
Created attachment 1925 
Backtrace of crash while opening tar.bz2

Xarchiver 0.5.0. rc1 crashed very often. This backtrace was generated from a crash that occurred while trying to open a tar.bz2. The file I tried to open is http://downloads.sourceforge.net/battery-4-xfce4/battery-applet-4-xfce4-0.9.1.tar.bz2
Comment 1 Giuseppe Torelli 2008-10-29 07:42:43 CET
$ src/xarchiver -e /media/sdb10/xa_archives/battery-applet-4-xfce4-0.9.1.tar.bz2 
Xarchiver 0.5.0svn-r27962 (©)2005-2008 Giuseppe Torelli
tar -xjvf /media/sdb10/xa_archives/battery-applet-4-xfce4-0.9.1.tar.bz2 --overwrite -C /media/sdb10/xa_extract_dir 
gt[xarchiver]$ ls /media/sdb10/xa_extract_dir/battery-applet-4-xfce4-0.9.1/
aclocal.m4    config.h.in   data                 intltool-merge.in   missing        src
AUTHORS       config.sub    depcomp              intltool-update.in  mkinstalldirs  TODO
ChangeLog     configure     INSTALL              ltmain.sh           NEWS
compile       configure.in  install-sh           Makefile.am         po
config.guess  COPYING       intltool-extract.in  Makefile.in         README
gt[xarchiver]$

No crash with the above revision. Please try with that revision. Thank you for notifying bugs, I appreciate your courtesy.
Comment 2 Christoph Wickert editbugs 2008-10-29 10:59:32 CET
Confirmed to be fixed in 0.5.0svn-r27962, but reopen the bug because latest svn r28502 crashes again on opening any archive type I have tested except zip. The backtrace is basically the same, tried with the archive from bug #4534,  https://belug.de/~beldi/releases/beldi-0.9.22.tgz
Comment 3 Christoph Wickert editbugs 2008-10-29 11:00:11 CET
Created attachment 1927 
Backtrace of crash while opening tar.gz
Comment 4 Christoph Wickert editbugs 2008-10-29 11:01:09 CET
REOPENED
Comment 5 Giuseppe Torelli 2008-10-29 11:06:49 CET
Christoph,  do you use a 64 bit environment? However the crash occur in the glib library not in xarchiver code:

Backtrace was generated from '/usr/bin/xarchiver'

[Thread debugging using libthread_db enabled]
[New Thread 0xb7f55b30 (LWP 22931)]
0x00110416 in __kernel_vsyscall ()
#0  0x00110416 in __kernel_vsyscall ()
#1  0x008aa233 in __waitpid_nocancel () from /lib/libc.so.6
#2  0x00a6bc97 in IA__g_spawn_sync (working_directory=<value optimized out>, 
    argv=<value optimized out>, envp=<value optimized out>, 
    flags=<value optimized out>, child_setup=<value optimized out>, 
    user_data=<value optimized out>, standard_output=<value optimized out>, 
    standard_error=<value optimized out>, exit_status=<value optimized out>, 
    error=<value optimized out>) at gspawn.c:374

Do you see the line above? The crash occurs in the glib source gspawn.c:374. I cannot reproduce such crash on my 32bit system.
Comment 6 Giuseppe Torelli 2008-10-29 22:15:21 CET
(In reply to comment #5)
> Christoph,  do you use a 64 bit environment? However the crash occur in the
> glib library not in xarchiver code:
> 
> Backtrace was generated from '/usr/bin/xarchiver'

This is weird. Can you send me a generated backtrace from the source directory please? This way the debug info are not stripped and the backtrace is really useful, thank you for your cooperation.

$ gdb src/xarchiver
Comment 7 Christoph Wickert editbugs 2008-10-29 22:26:17 CET
(In reply to comment #5)
> Christoph,  do you use a 64 bit environment? However the crash occur in the
> glib library not in xarchiver code:

No, as I said in the platform field I'm on i386. Packages/versions involved are:

# rpm -qa | grep debuginfo | sort
atk-debuginfo-1.22.0-1.fc9.i386
cairo-debuginfo-1.6.4-1.fc9.i386
glib2-debuginfo-2.16.6-1.fc9.i386
glibc-debuginfo-2.8-8.i686
glibc-debuginfo-common-2.8-8.i386
gtk2-debuginfo-2.12.12-1.fc9.i386
pango-debuginfo-1.20.4-1.fc9.i386

Sorry I cannot provide a backtrace, because now with r28503 it does not crash any more, so you can close this bug again if you want. Or do you want me to try with r28502 once more?
Comment 8 Giuseppe Torelli 2008-10-29 22:37:30 CET
(In reply to comment #7)

> Sorry I cannot provide a backtrace, because now with r28503 it does not crash
> any more, so you can close this bug again if you want. Or do you want me to try
> with r28502 once more?

Can you please try once more but with the latest revision, the 28505 ?

Thank you,
Giuseppe
Comment 9 Christoph Wickert editbugs 2008-10-29 23:40:22 CET
both 28505 as well as 28506 seem to be working reliably, thanks. I will close this bug now and eventually reopen if I experience crashes again.

Bug #4533

Reported by:
Christoph Wickert
Reported on: 2008-10-28
Last modified on: 2008-10-29

People

Assignee:
Giuseppe Torelli
CC List:
0 users

Version

Version:
0.5.0beta1

Attachments

Backtrace of crash while opening tar.bz2 (4.09 KB, text/plain)
2008-10-28 22:12 CET , Christoph Wickert
no flags
Backtrace of crash while opening tar.gz (4.05 KB, text/plain)
2008-10-29 11:00 CET , Christoph Wickert
no flags

Additional information