Jim Meyering wrote:
> Did you know that glibc's snprintf can fail due to ENOMEM?
FYI, this is because glibc's snprintf is a thin
wrapper around vasnprintf, and as its name implies,
that latter may well allocate heap storage.
However, "fixing" this problem in glibc would mean adapting
or cloning t
Ralf Wildenhues wrote:
> Hello,
>
> * Jim Meyering wrote on Sat, Nov 06, 2010 at 02:55:47PM CET:
>> Jim Meyering wrote:
>> > Andreas Schwab wrote:
>> >> Jim Meyering writes:
>> >>> cat <<\EOF > init.cfg
>> >>> f()
>> >>> {
>> >>> case $IFS in '') exit 91;; esac
>> >>> local s=$IFS
>> >>> cas
Hello,
* Jim Meyering wrote on Sat, Nov 06, 2010 at 02:55:47PM CET:
> Jim Meyering wrote:
> > Andreas Schwab wrote:
> >> Jim Meyering writes:
> >>> cat <<\EOF > init.cfg
> >>> f()
> >>> {
> >>> case $IFS in '') exit 91;; esac
> >>> local s=$IFS
> >>> case $s in '') exit 97;; esac
> >>> }
> >
Jim Meyering wrote:
> Andreas Schwab wrote:
>> Jim Meyering writes:
>>
>>> For the record, I reduced it to this,
>>> where /bin/sh is /usr/local/bin/bash, which is 4.1.7:
>
> Actually, /bin/sh is *not* bash on that particular system.
> Rather, it's simply FreeBSD 8.1's /bin/sh.
> That requires a
