[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: printf produces no output for %f directive
From: |
Jim Meyering |
Subject: |
Re: printf produces no output for %f directive |
Date: |
Fri, 19 Oct 2007 12:41:17 +0200 |
Bruno Haible <address@hidden> wrote:
> On a glibc 2.3.6 system, 'printf' produces no output for a %f directive in
> some cases:
>
> $ /packages/gnu/bin/printf --version
> printf (GNU coreutils) 6.9
> $ /packages/gnu/bin/printf %.100000000f 17
> <no output>
> $ echo $?
> 0
>
> I would have expected an error message and an exit status of 1.
>
> Likewise for %e instead of %f.
>
> 100000000 is far less than INT_MAX.
Thanks for the report.
On both fedora rawhide- and debian-unstable-based systems,
with coreutils-6.9 and the latest sources, I get this:
$ ./printf %.100000000f 17 |wc -c
100000003
maybe your libc is responsible?
- printf produces no output for %f directive, Bruno Haible, 2007/10/19
- Re: printf produces no output for %f directive,
Jim Meyering <=
- Re: printf produces no output for %f directive, Bruno Haible, 2007/10/19
- Re: printf produces no output for %f directive, Jim Meyering, 2007/10/19
- Re: printf produces no output for %f directive, Andreas Schwab, 2007/10/19
- Re: printf produces no output for %f directive, Eric Blake, 2007/10/19
- Re: printf produces no output for %f directive, Jim Meyering, 2007/10/19
- Re: printf produces no output for %f directive, Jim Meyering, 2007/10/19
- POSIX requires checking all *printf return values?!?, Jim Meyering, 2007/10/19
- Re: POSIX requires checking all *printf return values?!?, Pádraig Brady, 2007/10/19
- Re: POSIX requires checking all *printf return values?!?, Jim Meyering, 2007/10/19
- Re: POSIX requires checking all *printf return values?!?, Andreas Schwab, 2007/10/19