file-roller crashed with SIGSEGV in memmove()

Bug #428383 reported by DivineSpectrum
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: file-roller

ProblemType: Crash
Architecture: i386
Date: Sat Sep 12 15:09:26 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/file-roller
Package: file-roller 2.27.92-0ubuntu1
ProcCmdline: file-roller --default-dir=file:///home/User Name/Progetti --add file:///home/User Name/Progetti/lumiera%202
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
SegvAnalysis:
 Segfault happened at: 0xd5cb3a <memmove+58>: movsb %ds:(%esi),%es:(%edi)
 PC (0x00d5cb3a) ok
 source "%ds:(%esi)" (0x0091acf9) ok
 destination "%es:(%edi)" (0x0091acf9) in non-writable VMA region: 0x0054d000-0x009ae000 r-xp /usr/lib/libgtk-x11-2.0.so.0.1711.0
SegvReason: writing VMA /usr/lib/libgtk-x11-2.0.so.0.1711.0
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 memmove () from /lib/tls/i686/cmov/libc.so.6
 g_strchug () from /usr/lib/libglib-2.0.so.0
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: file-roller crashed with SIGSEGV in memmove()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

StacktraceTop:mempcpy () at ../sysdeps/i386/i686/mempcpy.S:49
?? () from /usr/lib/libgtk-x11-2.0.so.0
add_clicked_cb (widget=0x8f5c0f0, data=0x91ac7e)
IA__g_cclosure_marshal_VOID__VOID (closure=0x8f37068,
IA__g_closure_invoke (closure=0x8f37068, return_value=0x0,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in file-roller (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
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.