bug in libtre (regexp library) [was Re: sed broken]

["Pouya D. Tafti" <pouya%san-serriffe.org@localhost>]

After puzzling on this for quite some time, it eventually dawned on me
that I had enabled the TRE regexp library in mk.conf by adding to it
the line

    USE_LIBTRE=yes

Rebuilding libc without libtre appears to have resolved the issue.

Shall I file a PR?

Thank you all for your patience (with special thanks to everyone who
responded), and sorry about the noise.

Pouya


On 11 February 2011 15:34, Pouya D. Tafti <pouya%san-serriffe.org@localhost> 
wrote:
> The issue seems to be related to libc: ÂI had an old pkg_comp chroot
> jail lying around, and observed this:
>
> Â Âlaptop$ echo 'foo*bar' | /var/chroot/pkg_comp/test/usr/bin/sed
> 's/*/-/g'
> Â Â-f-o-o-*-b-a-r-
>
> BUT:
>
> Â Âlaptop$ echo 'foo*bar' |
> LD_LIBRARY_PATH=/var/chroot/pkg_comp/test/usr/lib
> /var/chroot/pkg_comp/test/usr/bin/sed 's/*/-/g'
> Â Âfoo-bar
>
> The newly rebuilt libc still fails with both the old and the new sed:
>
> Â Âlaptop$ echo 'foo*bar' | LD_LIBRARY_PATH=/usr/destdir/usr/lib
> /var/chroot/pkg_comp/test/usr/bin/sed 's/*/-/g'
> Â Â-f-o-o-*-b-a-r-
>
> Â Âlaptop$ echo 'foo*bar' | LD_LIBRARY_PATH=/usr/destdir/usr/lib
> /usr/tooldir/bin/nbsed 's/*/-/g'
> Â Â-f-o-o-*-b-a-r-
>
> Any suggestions what to try next? ÂRebuilding the system afresh
> doesn't seem to be helping much.
>
> Pouya
>
>
> On 11 February 2011 15:16, Paul Goyette <paul%whooppee.com@localhost> wrote:
>> On amd64, with tools from just a short while ago, I get
>>
>> Â Â Â Â# echo 'foo*bar' | ./tools/x86_64/amd64/bin/nbsed -e 's/*/-/g'
>> Â Â Â Âfoo-bar
>> Â Â Â Â#
>>
>> On Fri, 11 Feb 2011, Pouya D. Tafti wrote:
>>
>>> On 11 February 2011 14:55, Martin Husemann <martin%duskware.de@localhost> 
>>> wrote:
>>>>
>>>> On Fri, Feb 11, 2011 at 02:32:35PM +0100, Pouya D. Tafti wrote:
>>>>>
>>>>> Is anyone else seeing this? ÂShould I file a PR?
>>>>
>>>> I can't reproduce it with a -current updated ~two hours ago.
>>>
>>> Thank you.
>>>
>>> I just updated the sources, nuked /usr/objdir and /usr/tooldir, and
>>> started a fresh build without -u. ÂStill, with the freshly rebuilt
>>> /usr/tooldir/bin/nbsed I see:
>>>
>>> laptop$ echo 'foo*bar' | /usr/tooldir/bin/nbsed -e 's/*/-/g'
>>> -f-o-o-*-b-a-r-
>>>
>>> I'm at a complete loss as to what to do next...
>>>
>>> Pouya
>