Re: Weird background crashing bug

[Pierre Gaston]

On Mon, Jun 29, 2015 at 5:54 AM, Braden Best <bradentbest@gmail.com> wrote:

Re-send:

I noticed it when I tried to branch an xterm off into multiple sessions and mistyped its name:

`xter m&`

So after experimenting with a ton of different scenarios I've come to this conclusion:

* both xterm and gnome-terminal crash

* a nested bash session also crashes returning me back to the previous shell where the wd is ~

* does not crash in TTY, nor in nested session within TTY.

* only happens when two or more (but not less) directories deep into home (~), for example, "~/Videos/movies/" or "~/Pictures/vacation/2009".

Running a non-existent command in the background while two or more directories deep into home (~) causes bash to crash, but only when in a terminal emulator

Why does this happen?

Addendum:

The version number of Bash.
$ bash --version
4.3.11(1)-release (x86_64-pc-linux-gnu)

The hardware and operating system.
Aspire-XC-603G
Ubuntu 14.04.1 LTS

The compiler used to compile Bash.
can't find that information. `info bash | grep gcc` gives me nothing

A description of the bug behaviour.
Described Above

A short script or ‘recipe’ which exercises the bug and may be used to reproduce it.
$ mkdir dir1
$ mkdir dir1/dir2
$ cd dir1/dir2
$ nonexistentcommand &

Using it as a script won't cause a crash. The crash only happens in interactive mode.

On Sun, Jun 28, 2015 at 8:40 PM, Braden Best <bradentbest@gmail.com> wrote:

I noticed it when I tried to branch an xterm off into multiple sessions and mistyped its name:

`xter m&`

So after experimenting with a ton of different scenarios I've come to this conclusion:

* both xterm and gnome-terminal crash

* a nested bash session also crashes returning me back to the previous shell where the wd is ~

* does not crash in TTY, nor in nested session within TTY.

* only happens when two or more (but not less) directories deep into home (~), for example, "~/Videos/movies/" or "~/Pictures/vacation/2009".

Running a non-existent command in the background while two or more directories deep into home (~) causes bash to crash, but only when in a terminal emulator

Why does this happen?

--

Braden Best

bradentbest@gmail.com
(505) 692 0947

--

Braden Best

bradentbest@gmail.com
(505) 692 0947

I don't seem to be able to reproduce with 4.3.30(1)-release, just in case, can you try it after running: 

PS1='$ ' PROMPT_COMMAND=''; unset -f  command_not_found_handle