coco@cbnewsl.ATT.COM (felix.a.lugo) (12/01/89)
While fooling around with Steve Koren's SKSH (Release 1.2), I, actually my 20 month old son, discovered a problem in SKSH that will cause a "... Task Held ..." requester to pop-up. To reproduce the problem, simply type a command that is at least 48 characters long. Make sure the command does not exist so that SKSH will produce an error. For example, type (and press return), cccccccccccccccccccccccccccccccccccccccccccccccc at the SKSH prompt. The command name has to be at least 48 chars. long, the command line itself may be as long as SKSH allows. SKSH will immediately return an error message which looks like: cccccccccccccccccccccccccccccccccccccccccccccccc: Unable to execute program (24) and the stupid requester will attack you!!! 8^) I was able to determine that the problem occurs when the error message is 80 characters long (or more). I used "newzap" to NULL out the "Unable to execute ..." string, and was able to increase the command name. Since my son loves to "bang" on the keyboard whenever I move away from the computer, and since he always has a way to get to the RETURN key, this causes too many problems. _______________ Felix A. Lugo coco@ihlpy.att.com att!ihlpy!coco
koren@hpfelg.HP.COM (Steve Koren) (12/04/89)
[ amusing story of 20 month old son debugging SKsh deleted ]
Thanks; I'll fix it in 1.3. Buffer overflow problem.
- stevegilgalad@dip.eecs.umich.edu (Ralph Seguin) (06/10/90)
Anybody noticed a bug in using cp in SKsh? I used cp to copy a file to the floppy, and the file couldn't fit. It terminated sort of ok, but for some reason left a lock on the file so I couldn't remove it. Steve? Thanks, Ralph gilgalad@dip.eecs.umich.edu gilgalad@zip.eecs.umich.edu gilgalad@caen.engin.umich.edu Ralph_Seguin@ub.cc.umich.edu gilgalad@sparky.eecs.umich.edu USER6TUN@UMICHUB.BITNET Ralph Seguin | In order to get infinitely many monkeys to type 565 South Zeeb Rd. | something that actually makes sense, you need to Ann Arbor, MI 48103 | have infinitely many monkey editors as well. (313) 662-1506
kim@uts.amdahl.com (Kim DeVaughn) (06/10/90)
In article <2581@zipeecs.umich.edu>, gilgalad@dip.eecs.umich.edu (Ralph Seguin) writes: > Anybody noticed a bug in using cp in SKsh? I used cp to copy a file to > the floppy, and the file couldn't fit. It terminated sort of ok, but > for some reason left a lock on the file so I couldn't remove it. Steve? I'll answer this one, since Steve is probably out in the Colorado sun, and not working on SKsh 1.5 like he ought to be ... :-) ... He's aware of this problem, and will have it fixed in 1.5. Unfortunately, 1.5 may be delayed due to the problems he's having with Lattice v5.05 generating spurious F-line instructions in random places, for no apparent reason. He reported this problem to Lattice some time ago, but sofar, has heard nothing from them in the way of a fix, etc. /kim -- UUCP: kim@amdahl.amdahl.com or: {sun,decwrl,hplabs,pyramid,uunet,oliveb,ames}!amdahl!kim DDD: 408-746-8462 USPS: Amdahl Corp. M/S 249, 1250 E. Arques Av, Sunnyvale, CA 94086 BIX: kdevaughn GEnie: K.DEVAUGHN CIS: 76535,25
koren@hpfelg.HP.COM (Steve Koren) (06/11/90)
> He's aware of this problem, and will have it fixed in 1.5. Unfortunately, 1.5 > may be delayed due to the problems he's having with Lattice v5.05 generating > spurious F-line instructions in random places, for no apparent reason. I have a solution for the F instruction problem now. My *new* problem is that my Ami died :-( I don't know how long this will delay the 1.5 release of SKsh. It depends on the repair shop. - steve