https://bugzilla.novell.com/show_bug.cgi?id=765248
https://bugzilla.novell.com/show_bug.cgi?id=765248#c8
Stanislav Brabec changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |ASSIGNED
--- Comment #8 from Stanislav Brabec 2012-06-06 16:39:50 CEST ---
I tried both
sed -e '/^[*#;%]/d' -e 's@[ ?][ ?]*@ @g' -e '/^ *$/d' -e 's@ $@@' -e 's@ *" *@
" @g' -e 's@" \([^"]*\) "@"\1"@g'
and
sed -e 's@$@ %@' -e 's@^\(\([^ ]*\).*\)@\1\2@' -e 's@\(.*<\[* *\([^
]*\)\.enc\(.*\)\)@\1 \2@' -e '/%[^ ]*$/s@$@ default@' -e 's@\(.*<<* *\([^
]*\)\.pf[ab].*\)@\1 \2@' -e '/%[^ ]* [^ ]*$/s@\( \([^ ]*\).*\)$@\1 \2@' -e
's@\(.*[" ]\([.0-9-][.0-9-]*\) *ExtendFont.*\)@\1 -e \2@' -e 's@\(.*["
]\([.0-9-][.0-9-]*\) *SlantFont.*\)@\1 -s \2@' -e 's@.*%@@'
None of them crashes on random input. So it seems to be input dependent. Or you
have a different sed version.
I have openSUSE 12.1 x86_64, sed has version 4.2.1 release 5.1.2 (rpm -qi sed).
If you are able to find line where it crashes, you can change call of sed to
"valgrind sed". valgrind often correctly detects memory corruption before the
crash.
Otherwise I will try to write sed wrapper.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
