Non-existing executable causes bash to crash

Bug #1450489 reported by Till Halbach on 2015-04-30
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bash (Ubuntu)
High
Unassigned

Bug Description

The following line causes the bash to crash consistently.

foo.sh &> /dev/null &

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: bash 4.3-7ubuntu1.5
ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
Uname: Linux 3.13.0-49-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 30 16:13:18 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-11-21 (524 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: bash
UpgradeStatus: Upgraded to trusty on 2014-05-26 (339 days ago)

Till Halbach (till-halbach) wrote :
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, that doesn't seem to trigger a crash on wily, could you try with newer versions if that's still an issue for you?

Changed in bash (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Till Halbach (till-halbach) wrote :

No problem with
GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu).

Launchpad Janitor (janitor) wrote :

[Expired for bash (Ubuntu) because there has been no activity for 60 days.]

Changed in bash (Ubuntu):
status: Incomplete → Expired
Till Halbach (till-halbach) wrote :

Still a problem with version 4.3.11(1). That is the version the comes with Ubuntu 14.04 LTS.

This currently provides a reliable way to crash bash. I'm not sure about the implications, though.

Changed in bash (Ubuntu):
status: Expired → New
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers