Bruno Haible <[EMAIL PROTECTED]> writes:
> If you don't see the bug in Solaris, my guess is that either you
> have a symlink /bin/sh -> /bin/bash, or you have the coreutils
> 'printf' in your PATH in front of /usr/bin and /bin.
Thanks for catching this; yes, it's the latter that is the case.
I i
Paul Eggert wrote:
> +Large outputs may cause trouble. On Solaris 8 through 10, for example,
> +the command @samp{/bin/printf %01x 123} dumps core.
This holds also for Solaris 2.5.1 to Solaris 10.
> This particular
> +bug should have little practical effect since Solaris shells' builtin
> [E
Thanks, I installed this into the Autoconf manual:
2007-04-26 Paul Eggert <[EMAIL PROTECTED]>
* doc/autoconf.texi (Limitations of Builtins): Warn about Solaris
/bin/printf '%01x' 123. Problem reported by Arto C. Nirkko
via Bruno Haible.
Index: doc/autoconf.texi
===
The autoconf manual mentions two portability problem of the 'printf' command.
But there is a third one: a buffer overflow that crashes /bin/printf of
Solaris 9 and Solaris 10. Example (originally reported by
Arto C. Nirkko <[EMAIL PROTECTED]>):
$ /bin/printf '%01x' 123
Segmentation fault
$ t
