Jim Meyering wrote:
> I think I'll have to resort to using a moderately large width, yet
> with limited virtual memory, e.g., via ulimit -v 1.
Here is the beginning of a proposal for m4/printf.m4 along these lines.
*** m4/printf.m4.orig 2007-11-03 05:38:54.0 +0100
--- m4/printf.m4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 10/30/2007 7:29 PM:
> But for error-posix and verror-posix: Such a module would, on glibc systems,
> not only pull in vasnprintf but also replace the error() function. Do you
> really mean that?
Good question.
> Usually y
Eric Blake wrote:
> And we should probably do something similar by adding error-posix,
> verror-posix, and xvasprintf-posix. For example, m4 1.4.10 uses
> xvasprintf for its `format' builtin, and I had to manually pull in
> vasprintf-posix by looking at the implementation details of xvasprintf.c.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 10/30/2007 7:18 AM:
>> It's the xprintf.c code which calls vprintf(), bypassing printf(). Since
>> this is a detail that the gnulib user should not know about, we should
>> introduce a module 'xprintf-posix' that causes xpr
Bruno Haible <[EMAIL PROTECTED]> wrote:
>> >> freebsd$ ./printf %.2147483647f 1
>> >> Segmentation fault (core dumped)
>
> I reproduce on NetBSD 3.0, both with the system's printf program and with
> the coreutils printf.
>
> It dumps core for width 5000 but not for width 1000. Therfore
Hi Jim,
> >> freebsd$ ./printf %.2147483647f 1
> >> Segmentation fault (core dumped)
I reproduce on NetBSD 3.0, both with the system's printf program and with
the coreutils printf.
It dumps core for width 5000 but not for width 1000. Therfore I
think it's an unhandled out-of-memory c
Bruno Haible <[EMAIL PROTECTED]> wrote:
>> This is probably worth working around.
>> Maybe it's done already, but currently I've turned
>> off printf-posix in coreutils:
>>
>> freebsd$ ./printf %.2147483647f 1
>> Segmentation fault (core dumped)
>
> Before working around it in gnulib:
>
> - Wil
Hi Jim,
> This is probably worth working around.
> Maybe it's done already, but currently I've turned
> off printf-posix in coreutils:
>
> freebsd$ ./printf %.2147483647f 1
> Segmentation fault (core dumped)
Before working around it in gnulib:
- Will you turn on some *printf-posix in coreut
This is probably worth working around.
Maybe it's done already, but currently I've turned
off printf-posix in coreutils:
freebsd$ ./printf %.2147483647f 1
Segmentation fault (core dumped)
freebsd$ gdb --args ./printf %.2147483647f 1
GNU gdb 6.5
Copyright (C) 2006 Free Software Foundatio
