[BusyBox] bug#1132: BusyBox] bug#1132: Problem in sh when using '>' (0.50pre, cvs)

Fabrice Gautier gautier at email.enst.fr
Wed Mar 14 02:39:07 UTC 2001


On Tue, 13 Mar 2001 18:55:13 -0700
Erik Andersen <andersen at lineo.com> wrote:

> There have been a number of problems with the shell over the past few days.
> One of the hazards of development...  Anyway, I have just (within the last
> hour) checked in a large fix to the shell that takes care of all the problems I
> know of.  Could you try again with the latest from CVS? 

It's better but there's still a segfault problem.

I can reproduce it by doing this:

BusyBox v0.50pre (2001.03.14-02:16+0000) Built-in shell (lash)
Enter 'help' for a list of built-in commands.

/ # >
-sh: file name expected after
/ # a
Segmentation fault
root at droopy:~/rootfs # sh: a: No such file or directory

I build busybox with DDEBUG=true and ran it into gdb. And doing as above
i get:

0x8063b05 in insert_job (newjob=0xbffffbdc, inbg=0) at sh.c:1580
1580     for (thejob = job_list->head; thejob; thejob = thejob->next)

a (simplified) backtrace:

#0 insert_job (newjob=0xbffffbdc, inbg=0) at sh.c:1580
#1 run_command (newjob=0xbffffbdc, inbg=0, outpipe=0xbffffbc4) at
sh.c:1715
#2 busy_loop (input=0x40123880) at sh.c:1766

...

I have not the time to investigate further at the moment, but i may.

Regards,

-- 
Fabrice Gautier <gautier at email.enstfr>







More information about the busybox mailing list