This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Saving errno around signal handlers
- From: Roland McGrath <roland at hack dot frob dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: Florian Weimer <fweimer at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Tue, 11 Mar 2014 11:12:24 -0700 (PDT)
- Subject: Re: Saving errno around signal handlers
- Authentication-results: sourceware.org; auth=none
- References: <531077D9 dot 2000308 at redhat dot com> <20140228211938 dot B5FD5744B5 at topped-with-meat dot com> <53143F86 dot 6000201 at redhat dot com> <20140303234207 dot C6ED37444F at topped-with-meat dot com> <531570FE dot 3060100 at redhat dot com>
> > So the standard is not going to be changed to require that signal handling
> > save and restore errno implicitly. (It would have been a highly suspect
> > change.) It's being clarified to say that the implementation is free to do
> > so. But applications cannot assume any such thing, so any such future
> > application remains as broken as such applications are today. I see no
> > rationale even slightly compelling for making libc do this magic. In fact,
> > it would clearly do harm to people developing applications on glibc-based
> > systems but intending to write POSIX-conformant code.
>
> In that it would mask potential errors in the signal handling code?
Hide real bugs that many manifest on any POSIX-compliant system, yes.