From owner-freebsd-current@FreeBSD.ORG  Wed Apr  6 19:13:14 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id C286D16A4CE; Wed,  6 Apr 2005 19:13:14 +0000 (GMT)
Received: from imladris.teardrop.org (imladris.teardrop.org [66.92.66.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5EA2443D2F; Wed,  6 Apr 2005 19:13:14 +0000 (GMT)
	(envelope-from snow@teardrop.org)
Received: by imladris.teardrop.org (Postfix, from userid 100)
	id 335B4BE4BF; Wed,  6 Apr 2005 15:14:43 -0400 (EDT)
Date: Wed, 6 Apr 2005 15:14:43 -0400
From: James Snow <snow@teardrop.org>
To: Mike Jakubik <mikej@rogers.com>
Message-ID: <20050406191443.GA72359@teardrop.org>
References: <1724.172.16.0.199.1112814116.squirrel@wettoast.dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1724.172.16.0.199.1112814116.squirrel@wettoast.dyndns.org>
User-Agent: Mutt/1.4.2.1i
X-Mailman-Approved-At: Thu, 07 Apr 2005 15:33:31 +0000
cc: freebsd-current@freebsd.org
cc: freebsd-ports@freebsd.org
Subject: Re: Reproducible sig 11 with bash2
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2005 19:13:14 -0000

On Wed, Apr 06, 2005 at 03:01:56PM -0400, Mike Jakubik wrote:
> 
> I ran in to this odd problem by making a typo. By following the below
> steps, bash2 will exit with signal 11 and dump core. The user will get
> booted out of the system if it is their primary shell.

I've encountered a similar problem, also only present under -current. I
wasn't going to bother reporting it because, well, it's -current. But I
figured I'd at least corroborate your posting.

Write a short for loop, hit the up arrow to bring it back from command
history, make a change, hit return, dump core:

x40:~> bash
bash-2.05b$ for ((i=0; $i<2; i=$i+1))
> do
> echo $i
> done
0
1
bash-2.05b$ for ((i=0; $i<2; i=$i+1)); do echo 0$i; done
Bus error (core dumped)
x40:~>

I had thought about enabling debugging symbols in the bash port and
taking a stab at debugging it, but I haven't gotten around to it.


-Snow