Path: csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!usenet.stanford.edu!not-for-mail
From: isabella parakiss <izaberina@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: coredump with wait -n
Date: Sun, 23 Aug 2015 20:17:58 +0200
Lines: 28
Approved: bug-bash@gnu.org
Message-ID: <mailman.145.1440353882.11330.bug-bash@gnu.org>
References: <CAAZkfo+PhLwFZ_XD3-K70eumZfUHzs_h2DxrUzDhCWfJ2Bmytg@mail.gmail.com> <alpine.DEB.2.10.1508221632200.4115@chris.tor>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Cc: bug-bash <bug-bash@gnu.org>
To: "Chris F.A. Johnson" <chris@cfajohnson.com>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <alpine.DEB.2.10.1508221632200.4115@chris.tor>
Precedence: list
Xref: csiph.com gnu.bash.bug:11430

On 8/22/15, Chris F.A. Johnson <chris@cfajohnson.com> wrote:
> On Sat, 22 Aug 2015, isabella parakiss wrote:
>
>> Hi, after running wait -n there's something wrong, ^C doesn't work
>> properly anymore: it displays ^C in the readline buffer, but the current
>> line stays there until I press enter.  Running any command "fixes" it.
>>
>>
>> It can also dump core if you try with multiple jobs.
>>
>> $ bash --norc
>> bash-4.3$ sleep 1 & sleep 2 & wait -n
>> [1] 8368
>> [2] 8369
>> [1]-  Done                    sleep 1
>> bash-4.3$ ^C*** stack smashing detected ***: bash terminated
>
>     I have no problem running that line, and ^C still works.
>

I can provide additional infos if you tell me what to do.
I tried to reproduce it in gdb without much success, but anyway others
confirmed that bash crashes...


---
xoxo iza