Ubuntu
bash package

[apport] bash crashed with SIGSEGV

Bug #103632 reported by Lean Fuglsang on 2007-04-06

Affects		Status	Importance	Assigned to	Milestone
	bash (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Binary package hint: bash

Tried to apt-get a program, and uses tabcompletion.

ProblemType: Crash
Architecture: i386
Date: Fri Apr 6 10:38:41 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /bin/bash
Package: bash 3.2-0ubuntu6
PackageArchitecture: i386
ProcCmdline: bash
ProcCwd: /home/lean/development/f-spot/trunk
ProcEnviron:
SHELL=/bin/bash
LANG=da_DK.UTF-8
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
Signal: 11
SourcePackage: bash
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
Uname: Linux lean-laptop 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message

Lean Fuglsang (lean-ubuntu-cd) wrote on 2007-04-06:

Dependencies.txt Edit (463 bytes, text/plain; charset="utf-8")
Disassembly.txt Edit (537 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (2.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (664 bytes, text/plain; charset="utf-8")
Registers.txt Edit (497 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (263 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (290 bytes, text/plain; charset="utf-8")

Siegfried Gevatter (rainct) on 2007-12-08

Changed in bash:
importance:	Undecided → Medium

Revision history for this message

Sebastien Bacher (seb128) wrote on 2008-08-12:

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in bash:
status:	New → Incomplete

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2008-11-27:

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.