Re: bin/41764: ksh has suffered serious regressions in the past few years

[Robert Elz <kre%munnari.OZ.AU@localhost>]

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

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: bin/41764: ksh has suffered serious regressions in the past few 
years 
Date: Fri, 24 Jul 2009 04:44:14 +0700

     Date:        Thu, 23 Jul 2009 20:15:04 +0000 (UTC)
     From:        "Greg A. Woods" <woods%planix.com@localhost>
     Message-ID:  <20090723201504.504C563B913%www.NetBSD.org@localhost>
 
   |  The code as it was existed in NetBSD's 1.6.x and 2.0.x, and 2.1, and I
   |  don't recall anyone complaining of any actual crashes involving it.
 
 It may be almost (or completely) impossible to get a string ending with a
 backslash into ksh (or that part of it anyway) - just perhaps, if you have
 a potentially affected binary, you could try something like
 
        x='${c\'
        eval echo $x
 
 and see what happens, that'sjust about the only way I can imagine it getting
 through.
 
 This kind of thing isn't something an average user would likely encounter...
 
 kre