[BusyBox 0001505]: lash piping builtin causes random stops then segfault on fg
bugs at busybox.net
bugs at busybox.net
Fri Sep 21 05:09:03 PDT 2007
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=1505
======================================================================
Reported By: skissane
Assigned To: BusyBox
======================================================================
Project: BusyBox
Issue ID: 1505
Category: Documentation
Reproducibility: sometimes
Severity: crash
Priority: normal
Status: assigned
======================================================================
Date Submitted: 09-21-2007 05:09 PDT
Last Modified: 09-21-2007 05:09 PDT
======================================================================
Summary: 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.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
09-21-07 05:09 skissane New Issue
09-21-07 05:09 skissane Status new => assigned
09-21-07 05:09 skissane Assigned To => BusyBox
09-21-07 05:09 skissane File Added: lash-bug-typescript.txt
======================================================================
More information about the busybox-cvs
mailing list