On 02/22/2012 12:39 PM, Roland McGrath wrote: > Surely you can debug sed and discern > the exact sequence of library calls it's making.
That should be doable, yes, but it might be a lot of work and the patch is straightforward and appears correct. For now I installed the patch into gnulib, here: http://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=1997177209382391a38d061f234fe04c74b863da so that GNU applications on non-glibc platforms will get the fix. Stanislav, if you find a short and reproducible test case, please cc: it to bug-gnulib so that I can add it to the gnulib test cases too. Also, if you figure out what's causing sed to loop, that'd be even better: quite possibly it's another bug in the regex code, one that we should squash.
