xarchiver crashed with SIGSEGV in g_strconcat()

Bug #130722 reported by Shirish Agarwal
6
Affects Status Importance Assigned to Milestone
Xarchiver
Fix Released
Unknown
xarchiver (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: xarchiver

I was extracting a file when Xarchiver crashed.

ProblemType: Crash
Architecture: i386
Date: Tue Aug 7 00:54:10 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/xarchiver
NonfreeKernelModules: cdrom
Package: xarchiver 0.4.6-3ubuntu1
PackageArchitecture: i386
ProcCmdline: xarchiver --extract-to=/tmp /tmp/DpkgTerminalLog.gz
ProcCwd: /tmp
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_IN.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: xarchiver
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? ()
 g_strconcat () from /usr/lib/libglib-2.0.so.0
Title: xarchiver crashed with SIGSEGV in g_strconcat()
Uname: Linux Mugglewille 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Shirish Agarwal (shirishag75) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:xa_run_command (command=0x80a7f10 "cp -f /tmp/DpkgTerminalLog.gz /tmp", watch_child_flag=0) at callbacks.c:1983
gzip_bzip2_extract (archive=0x824c900, flag=1) at bzip2.c:104
xa_extract_single_files (archive=0x824c900, files=0x819eab0, path=0x824b120 "/tmp") at extract_dialog.c:616
main (argc=) at main.c:124
��������Dž\��������������� () from /lib/tls/i686/cmov/libc.so.6

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you for your bug report. I'm going to forward this upstream.

Changed in xarchiver:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Shirish have you been able to reproduce this ? If yes, how ? Could you give us the archive that made xarchiver crash ?

Revision history for this message
Shirish Agarwal (shirishag75) wrote :

Jerome,
            This is about 2 weeks or more so don't remember which archive it was which made xarchiver crash. You could either close down the bug or maybe I can try if the bug triggers again with some archive. If it does happen will give the info. here.

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you, in fact the backtrace contained enough information.

Changed in xarchiver:
status: Unknown → In Progress
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Upstream would like to know if this still happens with the current svn. Thank you.

Changed in xarchiver:
status: In Progress → Fix Released
Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

Fixed in jaunty with xarchiver 0.5.1.

Changed in xarchiver:
status: Triaged → Fix Released
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.