ports/73404: shells/ksh93 - notify option + output redirected to nonexistent file cause crash w/ segfault

[Parv]

The following reply was made to PR ports/73404; it has been noted by GNATS.

From: Parv <parv at pair.com>
To: Joe Kelsey <joe at zircon.seattle.wa.us>
Cc: freebsd-gnats-submit at 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 at 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
 
 --