On Thu, Jul 10, 2014 at 02:21:06PM -0700, Roland McGrath wrote:
> Is the SIGCHLD set with SA_RESTART?
>From what I see, no.
--
Richard Braun
> On Thu, Jul 10, 2014 at 02:21:06PM -0700, Roland McGrath wrote:
> > Is the SIGCHLD set with SA_RESTART?
>
> >From what I see, no.
Then potentially getting EINTR from lots of calls is what's expected.
The program should be fixed to use SA_RESTART if it is not expecting
to handle EINTR from nearl
On Thu, Jul 10, 2014 at 11:18:17PM +0200, Richard Braun wrote:
> All right, it looks like open() gets interrupted by SIGCHLD here. It's
> my understanding that signal handling is highly system-specific in such
> cases, but we probably want to align on what others do, as usual.
By the way, it looks
> On Mon, Jul 07, 2014 at 01:29:20PM +0200, Svante Signell wrote:
> > ./test.sh: 6: ./test.sh: cannot create /dev/null: Interrupted system
>
> All right, it looks like open() gets interrupted by SIGCHLD here. It's
> my understanding that signal handling is highly system-specific in such
> cases, b
On Mon, Jul 07, 2014 at 01:29:20PM +0200, Svante Signell wrote:
> ./test.sh: 6: ./test.sh: cannot create /dev/null: Interrupted system
All right, it looks like open() gets interrupted by SIGCHLD here. It's
my understanding that signal handling is highly system-specific in such
cases, but we probab
Plus I'm getting some weird errors. Can you help me figure out what they
mean?
There are three errors listed here - http://pastebin.com/cmH8Zf1g
20: I mailed about it earlier.
25: This one I don't get.
32: Seems like I need to add a VGO_gnu case and an appropriate
definition for VG_UCONTEXT_
