This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: [Various] libc/1828: signal handler chages errno while doing fdopen(3) to pipe.
- To: libc-alpha Mailinglist <libc-alpha at sourceware dot cygnus dot com>
- Subject: Re: [Various] libc/1828: signal handler chages errno while doing fdopen(3) to pipe.
- From: Andreas Schwab <schwab at suse dot de>
- Date: Tue, 25 Jul 2000 10:19:29 +0200
- Cc: Junjiro Okajima <j-okajim at nskli014 dot nsk dot nis dot nec dot co dot jp>
- References: <u81z0ihebk.fsf@gromit.rhein-neckar.de>
Andreas Jaeger <aj@suse.de> writes:
|> We've received the appended bug report which I've answered directly
|> with a reference to ISO C99.
|>
|> Looking again into it, I noticed that Unix98 and Posix allow to call
|> certain asynch-signal safe functions - which might set errno as a side
|> effect.
But SUS2 also says (sigaction/APPLICATION USAGE):
Note in particular that even the "safe" functions may modify errno; the
signal-catching function, if not executing as an independent thread, may
want to save and restore its value.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labs completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg