0001126: trap in ash broken, busybox-1.3.0 - 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

0001126

[BusyBox] Other

minor

always

12-22-06 00:03

12-22-06 17:27

Reporter

espakman

View Status

public

Assigned To

BusyBox

Priority

normal

Resolution

fixed

Status

closed

Product Version

Summary

0001126: trap in ash broken, busybox-1.3.0

Description

Somewhere between bb 1.2.2.1 and 1.3.0 the trap implementation in ash got broken.

When using "trap" in a script with busybox ash:
trap "rm -rf /tmp/*" EXIT
The response is:
"trap: 34: EXIT: bad trap"
(34 is the linenumber in the script)

Revision 15687 introduces this bug (rewrite of u_signal_names and decode_signal).

Additional Information

Attached Files

u_signal_names.c [^] (1,484 bytes) 12-22-06 06:56

busybox-signal.patch [^] (1,147 bytes) 12-22-06 14:31

Relationships

Notes
(0001926) LUDER 12-22-06 06:55	read all signal number and now "EXIT", INT , or SIGINT.

(0001927) LUDER 12-22-06 06:59	Now this file work Signal number: 0, 2 etc... and now EXIT INT or SIGINT

(0001928) espakman 12-22-06 14:32	Luder's file fixes the problem, attached an unified diff of this file.

(0001929) vda 12-22-06 17:27	Fixed in rev 17061, thanks

Issue History
Date Modified	Username	Field	Change
12-22-06 00:03	espakman	New Issue
12-22-06 00:03	espakman	Status	new => assigned
12-22-06 00:03	espakman	Assigned To	=> BusyBox
12-22-06 06:55	LUDER	Note Added: 0001926
12-22-06 06:56	LUDER	File Added: u_signal_names.c
12-22-06 06:59	LUDER	Note Added: 0001927
12-22-06 14:31	espakman	File Added: busybox-signal.patch
12-22-06 14:32	espakman	Note Added: 0001928
12-22-06 17:27	vda	Status	assigned => closed
12-22-06 17:27	vda	Note Added: 0001929
12-22-06 17:27	vda	Resolution	open => fixed