[BusyBox 0001311]: sed incorrectly parses command file
bugs at busybox.net
bugs at busybox.net
Thu Apr 12 22:01:52 UTC 2007
A NOTE has been added to this issue.
======================================================================
http://busybox.net/bugs/view.php?id=1311
======================================================================
Reported By: kiltedknight
Assigned To: BusyBox
======================================================================
Project: BusyBox
Issue ID: 1311
Category: Other
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 04-12-2007 14:24 PDT
Last Modified: 04-12-2007 15:01 PDT
======================================================================
Summary: sed incorrectly parses command file
Description:
When running the command "sed -f cmds.sed < input > output" with cmds.sed
containing:
s/^[^:]*: *//
s/\s*\\$//
s/\s*\([-./[:alnum:]_]\+\)/\1:\
/g
It will produce the error:
sed: unmatched '/'
When going through the code in sed.c, I discovered that it was attempting
to parse only the "/g" portion of the final command.
======================================================================
----------------------------------------------------------------------
kiltedknight - 04-12-07 15:01
----------------------------------------------------------------------
This bug is against the current version (1.5.0)
Issue History
Date Modified Username Field Change
======================================================================
04-12-07 14:24 kiltedknight New Issue
04-12-07 14:24 kiltedknight Status new => assigned
04-12-07 14:24 kiltedknight Assigned To => BusyBox
04-12-07 14:24 kiltedknight File Added: bb_sed_fix.diff
04-12-07 14:24 kiltedknight Issue Monitored: kiltedknight
04-12-07 15:01 kiltedknight Note Added: 0002309
======================================================================
More information about the busybox-cvs
mailing list