Ubuntu
filezilla package

filezilla crashed with SIGSEGV in memmove()

Bug #421386 reported by col reilly on 2009-08-30

This bug report is a duplicate of: Bug #421208: filezilla crashed with SIGSEGV in dbus_connection_dispatch(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	filezilla (Ubuntu)	Incomplete	Medium	Unassigned

Bug Description

Binary package hint: filezilla

crash when attempting to connect to a local sftp server when the domain name wasn't in /etc/hosts

ProblemType: Crash
Architecture: i386
Date: Sun Aug 30 10:30:53 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/filezilla
NonfreeKernelModules: wl
Package: filezilla 3.2.7.1-1
ProcCmdline: filezilla
ProcEnviron:
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
SegvAnalysis:
Segfault happened at: 0xf7cb23 <memmove+35>: rep movsl %ds:(%esi),%es:(%edi)
PC (0x00f7cb23) ok
source "%ds:(%esi)" (0x0a3c007b) not located in a known VMA region (needed readable region)!
destination "%es:(%edi)" (0x0a3bff9f) ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: filezilla
StacktraceTop:
memmove () from /lib/tls/i686/cmov/libc.so.6
?? () from /lib/libdbus-1.so.3
?? () from /lib/libdbus-1.so.3
?? () from /lib/libdbus-1.so.3
?? () from /lib/libdbus-1.so.3
Title: filezilla crashed with SIGSEGV in memmove()
Uname: Linux 2.6.31-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

col reilly (lupinehorror) wrote on 2009-08-30:

Dependencies.txt Edit (3.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (700 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (25.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (758 bytes, text/plain; charset="utf-8")
Registers.txt Edit (501 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (849 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (5.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-08-30: Stacktrace.txt (retraced)

Stacktrace.txt (retraced) Edit (1.8 KiB, text/plain)

StacktraceTop:memmove () at ../sysdeps/i386/i686/memmove.S:68
delete (real=0x9ba8d54, start=<value optimized out>,
_dbus_message_loader_queue_messages (loader=0x9ba8d50)
_dbus_transport_get_dispatch_status (transport=0x9bcffe8)
_dbus_transport_queue_messages (transport=0x9bcffe8)

Revision history for this message

Apport retracing service (apport) wrote on 2009-08-30: ThreadStacktrace.txt (retraced)

ThreadStacktrace.txt (retraced) Edit (15.4 KiB, text/plain)

Changed in filezilla (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Adrien Cunin (adri2000) on 2009-09-21

visibility:

private → public

Revision history for this message

Adrien Cunin (adri2000) wrote on 2009-09-29:

Thanks for reporting this bug. When exactly did this crash happen? If you can reproduce it, please tell us step by step how to do. This will make it easier for us to track down the problem and eventually fix it.