gnome-commander crashed with SIGSEGV in start_thread()

Bug #651061 reported by Raivis Rengelis
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
GNOME Commander
Fix Released
Critical
Mago
New
Undecided
Unassigned
gnome-commander (Debian)
Fix Released
Undecided
Unassigned
gnome-commander (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: gnome-commander

file search was running and I hit Esc mid-search

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-commander 1.2.8.8-2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Wed Sep 29 14:49:35 2010
ExecutablePath: /usr/bin/gnome-commander
ProcCmdline: gnome-commander
SegvAnalysis:
 Segfault happened at: 0x80bc1d0: mov 0x2c(%eax),%eax
 PC (0x080bc1d0) ok
 source "0x2c(%eax)" (0x0000002c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-commander
StacktraceTop:
 ?? ()
 ?? () from /lib/libglib-2.0.so.0
 start_thread () from /lib/libpthread.so.0
 clone () from /lib/libc.so.6
Title: gnome-commander crashed with SIGSEGV in start_thread()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Raivis Rengelis (raivisr) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 perform_search_operation (data=0x904d550)
 ?? () from /lib/libglib-2.0.so.0
 start_thread () from /lib/libpthread.so.0
 clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-commander (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Changed in gnome-commander (Ubuntu):
status: New → Confirmed
Changed in gnome-commander:
importance: Unknown → Medium
status: Unknown → New
Changed in gnome-commander:
importance: Medium → Unknown
status: New → Unknown
Changed in gnome-commander:
importance: Unknown → Critical
status: Unknown → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

Based off the comments in the upstream bug report:

Steps:
- go to Edit - Search (alt+f7)
- Search for any files (example test.py)
- check search recursive
- Press Find Button
- later press Close
Crash

It seems to me that a test case could be written for this in mago.

Changed in gnome-commander:
status: Confirmed → Incomplete
Changed in gnome-commander:
status: Incomplete → Confirmed
Revision history for this message
Alessio Treglia (quadrispro) wrote :

Fixed in Debian:

gnome-commander 1.2.8.11-3

Changed in gnome-commander (Debian):
status: New → Fix Released
Changed in gnome-commander:
status: Confirmed → Fix Released
Changed in gnome-commander (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.