|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ View Advanced ]
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Reproducibility |
Date Submitted |
Last Update |
|
0001505 |
[BusyBox] Documentation |
crash |
sometimes |
09-21-07 05:09 |
02-12-08 02:35 |
|
|
Reporter |
skissane |
View Status |
public |
|
|
Assigned To |
BusyBox |
|
Priority |
normal |
Resolution |
no change required |
|
|
Status |
closed |
|
Product Version |
svn |
|
|
Summary |
0001505: lash piping builtin causes random stops then segfault on fg |
|
Description |
Run lash. Try piping builtin commands through less (e.g. help, pwd, etc.). You may have to try a few times, or run a few other commands first -- its a bit random. Note in this case I am using standard less, not busybox less. Quickly you will find that when less exits, it spuriously comes up as Stopped, even though in fact it is exited. Then fg the job it claims to have stopped, and you will get a segfault. |
|
Additional Information |
See attached typescript containing demonstration of problem. |
|
|
Attached Files |
 lash-bug-typescript.txt [^] (2,564 bytes) 09-21-07 05:09 |
|
|
Relationships 
