Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #11426
| From | "Chris F.A. Johnson" <chris@cfajohnson.com> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: coredump with wait -n |
| Date | 2015-08-22 16:34 -0400 |
| Message-ID | <mailman.98.1440275657.11330.bug-bash@gnu.org> (permalink) |
| References | <CAAZkfo+PhLwFZ_XD3-K70eumZfUHzs_h2DxrUzDhCWfJ2Bmytg@mail.gmail.com> |
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.
--
Chris F.A. Johnson, <http://cfajohnson.com>
Back to gnu.bash.bug | Previous | Next | Find similar
Re: coredump with wait -n "Chris F.A. Johnson" <chris@cfajohnson.com> - 2015-08-22 16:34 -0400
csiph-web