Re: perror bug

On 2011-14-03 I wrote in : > 2) The perror replacement uses strerror, thus clobbering the strerror > buffer. > 3) On Cygwin, perror clobbers the strerror buffer. > > The fix for 2) should be to change lib/perror.c to call

Re: perror bug

> +# elif defined __sgi || (defined __sun && !defined _LP64) /* IRIX, Solaris > <= 9 32-bit */ > + > +    /* For a valid error number, the system's strerror() function returns > +       a pointer to a not copied string, not to a buffer.  */ Just for reference: How to find out whether a closed-sou

Re: perror bug

> >   1) The strerror_r replacement, when EXTEND_STRERROR_R is defined, > >      clobbers the strerror function's buffer, which it shouldn't. Here's a followup that tries harder to clobber the strerror function's buffer. It still is not possible on Solaris <= 9 in 64-bit mode, because that libc do

Re: perror bug

On 2011-14-03 I wrote in : > With gnulib, there are three problems > in toto: >   1) The strerror_r replacement, when EXTEND_STRERROR_R is defined, >      clobbers the strerror function's buffer, which it shouldn't. >   2) The perr

Re: perror bug

Eric Blake wrote on 2011-02-10: > POSIX requires that this program have an identical first and last line: > > #include > #include > #include > int main (void) { > char *err = strerror(1000); > printf ("%s\n", err); > errno = 2000; > perror ("hi"); > printf ("%s\n", err); > return 0;

Re: perror bug

On 02/09/2011 05:48 PM, Eric Blake wrote: > POSIX requires that this program have an identical first and last line: > > #include > #include > #include > int main (void) { > char *err = strerror(1000); > printf ("%s\n", err); > errno = 2000; > perror ("hi"); > printf ("%s\n", err); >