[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <jed4sgjkhh.fsf@sykes.suse.de>
Date: Sat, 05 Jan 2008 17:38:34 +0100
From: Andreas Schwab <schwab@...e.de>
To: "Phil Endecott" <phil_wueww_endecott@...zphil.org>
Cc: "Jiri Slaby" <jirislaby@...il.com>, <linux-kernel@...r.kernel.org>,
" Frederik Deweerdt" <deweerdt@...e.fr>
Subject: Re: strace, accept(), ERESTARTSYS and EINTR
"Phil Endecott" <phil_wueww_endecott@...zphil.org> writes:
> However, there's a lot of code and I know that there are bugs in it. I
> just want to focus on the kernel-related issue that the strace fragment
> that I posted brings up: even if my user code gets completely screwed up
> (corrupts its stack, runs out of FDs/VM/threads etc), I don't think that I
> should see in the strace output that accept() has returned
> ERESTARTSYS.
strace always sees the raw return value, before the signal handler is
executed and before the check for syscall restart is done.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@...e.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists