* select returns unexpected errno 514 on signal (Linus was going to fix this?)
@ 2004-04-14 16:10 Andrew Walrond
0 siblings, 0 replies; only message in thread
From: Andrew Walrond @ 2004-04-14 16:10 UTC (permalink / raw)
To: linux-kernel
When debugging (with gdb) a usermode program which receives a signal during
select(), select returns -1 and sets errno to 514, rather than the expected
EINTR.
Googling finds this reply from Linus to a similar thread a couple years ago,
which seems to suggest a patch was to be applied. If so, it hasn't been (this
machine is running 2.6.3)
--------------------------
On Thu, 15 Aug 2002, Brian Wellington wrote:
>
> If that's the case, then how does
> fprintf(stderr, "select: %s\n", strerror(errno));
> print
> select: Unknown error 514
> ?
>
> That's the traced process printing the error, not the tracing process.
Ahh, dang, there's a patch floating around for this case. Basically,
tracing interferes with the normal behaviour (ie you _shouldn't_ see this
normally, only when tracing system calls).
linus
-------------------------
Andrew Walrond
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-04-14 16:10 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-04-14 16:10 select returns unexpected errno 514 on signal (Linus was going to fix this?) Andrew Walrond
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®