0004094: The sh "continue" statement doesn't work - BusyBox Bug and Patch Tracking

BusyBox Bug and Patch Tracking

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0004094

[BusyBox] Other

major

always

07-14-08 15:48

07-14-08 21:52

Reporter

View Status

public

Assigned To

BusyBox

Priority

normal

Resolution

unable to reproduce

Status

closed

Product Version

Summary

0004094: The sh "continue" statement doesn't work

Description

When I run this script:

#!/bin/sh

while true; do
        sleep 1
        for iter in 1 2 ; do
                echo one
                continue
                echo two
        done
done

I get this output:

one
one
one
PX: not found
two
one
PX: not found
two
one
SIGSEGV

The details will vary depending on the number of items in the for loop.

Additional Information

This is the version included in the ELDK 4.0. Sorry I don't have a more precise version number, but the version fields in busybox itself are null in the build I'm using. (But, the version details are minor in this case, since it's so trivial to test its reproducibility.)

Attached Files

Relationships

Notes
(0009274) jo 07-14-08 15:49 edited on: 07-14-08 15:50	Whoops, forgot to mention, this is running on MIPS.

(0009284) vda 07-14-08 21:51	Current svn: # ./busybox ash z one one one one one one one one ^C # ./busybox msh z one one one one one one ^C # ./busybox hush z one hush: cannot exec 'continue': No such file or directory two one hush: cannot exec 'continue': No such file or directory two one hush: cannot exec 'continue': No such file or directory two one hush: cannot exec 'continue': No such file or directory two ^C

(0009294) vda 07-14-08 21:52	Unable to reproduce on current svn

Issue History
Date Modified	Username	Field	Change
07-14-08 15:48	jo	New Issue
07-14-08 15:48	jo	Status	new => assigned
07-14-08 15:48	jo	Assigned To	=> BusyBox
07-14-08 15:49	jo	Note Added: 0009274
07-14-08 15:50	jo	Note Edited: 0009274
07-14-08 15:50	jo	Issue Monitored: jo
07-14-08 21:51	vda	Note Added: 0009284
07-14-08 21:52	vda	Status	assigned => closed
07-14-08 21:52	vda	Note Added: 0009294
07-14-08 21:52	vda	Resolution	open => unable to reproduce