From owner-freebsd-ports-bugs@FreeBSD.ORG Wed Dec 8 05:00:55 2004 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A469916A4CF for ; Wed, 8 Dec 2004 05:00:55 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F24443D49 for ; Wed, 8 Dec 2004 05:00:55 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iB850t0C062355 for ; Wed, 8 Dec 2004 05:00:55 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iB850tQH062354; Wed, 8 Dec 2004 05:00:55 GMT (envelope-from gnats) Date: Wed, 8 Dec 2004 05:00:55 GMT Message-Id: <200412080500.iB850tQH062354@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Parv Subject: Re: ports/73404: shells/ksh93 - notify option + output redirected to nonexistent file cause crash w/ segfault X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Parv List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 05:00:55 -0000 The following reply was made to PR ports/73404; it has been noted by GNATS. From: Parv To: Joe Kelsey Cc: freebsd-gnats-submit@freebsd.org Subject: Re: ports/73404: shells/ksh93 - notify option + output redirected to nonexistent file cause crash w/ segfault Date: Tue, 7 Dec 2004 23:56:48 -0500 in message <1102478713.616.140.camel@zircon.zircon.seattle.wa.us>, wrote Joe Kelsey thusly... > > Unfortunately, you do not present enough information for me to > actually reporduce your problem. > > I am uncertain exactly what method you use to actually invoke > ksh93 and cause it to dump core. ... > If you can give me an actual command line which causes the > problem, then maybe I can attempt to debug the problem. Simply > stating that you invoke it from bash really is not helpful. The PR has everything in it. Yes, simply invoking from another (interactive) shell does not cause crash, only under a particular situation. To reiterate & rephrase, edit "~/.profile" to have ... ENV="${HOME}/.kshrc-segfault" export ENV rm -f initially-nonexistent-file > initially-nonexistent-file & exec $0 ... and, edit "~/.kshrc-segfault" to have only ... set -o notify ... then in an interactive shell (tcsh, sh, bash, ksh93), type the following in order ... ksh93 # run ksh93 under another shell . ~/.profile # source ~/.profile under ksh93 ...which ends in a crash, if the first time does not produce crash, 2d time sure does. Following was also tried, in order, just in case, resulting in the same... # Change tcsh to sh, bash, or even ksh93 (in which case, no need for # the 2d step) xterm -e tcsh # 1 ksh93 # 2 . ~/.profile # 3 - Parv --