Path: csiph.com!xmission!news.glorb.com!usenet.stanford.edu!not-for-mail
From: "Chris F.A. Johnson" <chris@cfajohnson.com>
Newsgroups: gnu.bash.bug
Subject: Re: coredump with wait -n
Date: Sat, 22 Aug 2015 16:34:01 -0400 (EDT)
Lines: 21
Approved: bug-bash@gnu.org
Message-ID: <mailman.98.1440275657.11330.bug-bash@gnu.org>
References: <CAAZkfo+PhLwFZ_XD3-K70eumZfUHzs_h2DxrUzDhCWfJ2Bmytg@mail.gmail.com>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Trace: usenet.stanford.edu 1440275658 28676 208.118.235.17 (22 Aug 2015 20:34:18 GMT)
X-Complaints-To: action@cs.stanford.edu
To: bug-bash <bug-bash@gnu.org>
Envelope-to: bug-bash@gnu.org
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpcorp.com; s=a0-2; h=Feedback-ID:X-Smtpcorp-Track:Message-ID:Subject:To: From:Date; bh=yb+t36Qj/KSfuhDvthI9OHQx+/QOL45k/bJMguBCPls=; b=IW5ZDxqLEneiXQK s9C9jXl7n4SIA6TAWGWovcJbFHxMrH7KdPazJ9EIajGkQSxx3ntsgC/aMEseOBhzeFomWzJy+3Tqq ViuH7kbONbq2vos4968LaCVVafDJoFJ9+jUXVwbRWQHW88oJtOh/Vx3ILALWeXxqb8TXyBWChYiOM 47IcX7IMLUreeXA52LPqdZHbPlFkpFiz2mq6cGW4VVEBgEPYIzTsaWW5JXbJQzJQRC+Hns9cczpiw 3UtuwPDgXzx3YKTt4ZLgfwSsDbty6yp7xOiLQQGwdJO8OF7Iy9DtcbEpuqnRLg0Nz0iBGFzkBn1qP U2bC1kxhNrMbPxbog6Q==;
X-X-Sender: chris@chris.tor
In-Reply-To: <CAAZkfo+PhLwFZ_XD3-K70eumZfUHzs_h2DxrUzDhCWfJ2Bmytg@mail.gmail.com>
User-Agent: Alpine 2.10 (DEB 1266 2009-07-14)
X-Smtpcorp-Track: 1ZTFleNRKGfhuQ.2uzjBcHc5
Feedback-ID: 124612m:124612a-vpTX9:124612sXH7J4NeWF:SMTPCORP
X-Report-Abuse: Please forward a copy of this message, including all headers, to <abuse@smtp2go.com>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x
X-Received-From: 216.22.15.234
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-bash>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
Xref: csiph.com gnu.bash.bug:11426

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>