file-roller crashed with SIGSEGV in memmove()

Bug #422740 reported by h1l4nd0r
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: file-roller

more logs

ProblemType: Crash
Architecture: amd64
Date: Tue Sep 1 22:36:12 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/file-roller
Package: file-roller 2.27.91-0ubuntu1
ProcCmdline: file-roller --default-dir=file:///home/username/Desktop --add file:///home/username/Desktop/%D0%9F%D1%81%D0%B8%D1%85%D0%BE%D0%BB%D0%BE%D0%B3%D0%B8%D1%8F%20%D0%B2%D0%BB%D0%B8%D1%8F%D0%BD%D0%B8%D1%8F.doc
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
SegvAnalysis:
 Segfault happened at: 0x7fb3df205f27 <memmove+343>: mov %dl,0x0(%rbp)
 PC (0x7fb3df205f27) ok
 source "%dl" ok
 destination "0x0(%rbp)" (0x7fb3e0e640d2) in non-writable VMA region: 0x7fb3e0aaf000-0x7fb3e0ef9000 r-xp /usr/lib/libgtk-x11-2.0.so.0.1709.0
SegvReason: writing VMA /usr/lib/libgtk-x11-2.0.so.0.1709.0
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 memmove () from /lib/libc.so.6
 g_strchug () from /usr/lib/libglib-2.0.so.0
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: file-roller crashed with SIGSEGV in memmove()
Uname: Linux 2.6.31-8-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
h1l4nd0r (chupan) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:*__GI_memmove (dest=0x7fb3e0e640d2,
IA__g_strchug (string=0x7fb3e0e640d2 "")
add_clicked_cb (widget=<value optimized out>,
IA__g_closure_invoke (closure=0x1985df0,
signal_emit_unlocked_R (node=0x15a6890,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in file-roller (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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.

Changed in file-roller (Ubuntu):
status: New → Invalid
visibility: private → public
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.