Re: Small test example for: cannot create /dev/null: Interrupted system call

2014-07-20 Thread Samuel Thibault
Hello, Thanks for your investigation, I have submitted a bug report against dash. Samuel

Re: Small test example for: cannot create /dev/null: Interrupted system call

2014-07-11 Thread Svante Signell
On Fri, 2014-07-11 at 10:30 +0200, Svante Signell wrote: > On Fri, 2014-07-11 at 10:13 +0200, Thomas Schwinge wrote: > > Hi! > > > Hi Thomas, the shell I use is dash. > > Some further tests: > > Linux: > ./test_interrupted_system_call.sh > ./test_interrupted_system_call.bash > ./test_interrupte

Re: Small test example for: cannot create /dev/null: Interrupted system call

2014-07-11 Thread Svante Signell
On Fri, 2014-07-11 at 10:13 +0200, Thomas Schwinge wrote: > Hi! > > On Thu, 10 Jul 2014 23:26:24 +0200, Richard Braun wrote: > > 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

Re: Small test example for: cannot create /dev/null: Interrupted system call

2014-07-11 Thread Thomas Schwinge
Hi! On Thu, 10 Jul 2014 23:26:24 +0200, Richard Braun wrote: > 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 pr

Re: Small test example for: cannot create /dev/null: Interrupted system call

2014-07-10 Thread 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. -- Richard Braun

Re: Small test example for: cannot create /dev/null: Interrupted system call

2014-07-10 Thread Roland McGrath
> 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

Re: Small test example for: cannot create /dev/null: Interrupted system call

2014-07-10 Thread Richard Braun
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

Re: Small test example for: cannot create /dev/null: Interrupted system call

2014-07-10 Thread Roland McGrath
> 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

Re: Small test example for: cannot create /dev/null: Interrupted system call

2014-07-10 Thread Richard Braun
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

Re: Small test example for: cannot create /dev/null: Interrupted system call

2014-07-08 Thread Svante Signell
On Mon, 2014-07-07 at 13:29 +0200, Svante Signell wrote: > Hi, > > found out when running the testsuite for elfutils that the following > code reproducibly triggers the interrupted system call bug: > > #! /bin/sh > > echo 'mai

Small test example for: cannot create /dev/null: Interrupted system call

2014-07-07 Thread Svante Signell
Hi, found out when running the testsuite for elfutils that the following code reproducibly triggers the interrupted system call bug: #! /bin/sh echo 'main () { while (1) pause (); }' > native.c gcc -o native -g native.c > /dev/