Bug 603531 - [abrt] crash in gvfs-1.6.1-3.fc13: malloc_consolidate: Process /usr/libexec/gvfsd-sftp was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gvfs-1.6.1-3.fc13: malloc_consolidate: Process /usr/libexec/g...
Keywords:
Status: CLOSED DUPLICATE of bug 609133
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e155f19a8036b9799b20dc869a6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-13 18:13 UTC by Damien Grassart
Modified: 2015-03-03 22:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 19:48:26 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (33.90 KB, text/plain)
2010-06-13 18:13 UTC, Damien Grassart 		no flags Details
View All

Description Damien Grassart 2010-06-13 18:13:47 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-sftp --spawner :1.7 /org/gtk/gvfs/exec_spaw/5
component: gvfs
crash_function: malloc_consolidate
executable: /usr/libexec/gvfsd-sftp
global_uuid: e155f19a8036b9799b20dc869a6245b234b3ae01
kernel: 2.6.33.5-112.fc13.x86_64
package: gvfs-1.6.1-3.fc13
rating: 4
reason: Process /usr/libexec/gvfsd-sftp was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Tried to connect to a remote machine via sftp (sftp://netbook/)
2.
3.
Comment 1 Damien Grassart 2010-06-13 18:13:49 UTC 
Created attachment 423664 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 19:48:26 UTC 

*** This bug has been marked as a duplicate of bug 609133 ***
Comment 3 Karel Klíč 2010-11-08 19:48:26 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #609133.

Sorry for the inconvenience.
Note You need to log in before you can comment on or make changes to this bug.