Re: interrupted system call when using named pipes on FreeBSD

2013-02-04 Thread Chet Ramey
On 2/4/13 7:30 AM, Lionel Cons wrote: >> It seems like implementations are buggy enough that bash needs to do >> something to work around them, but this isn't exactly it. >> >> The issue with the proposed patch is that it would make it impossible to >> interrupt an open using, say, ^C. There need

Re: interrupted system call when using named pipes on FreeBSD

2013-02-04 Thread Lionel Cons
On 30 January 2013 17:48, Chet Ramey wrote: >> a simple patch to workaround/fix the issue by Yuta SATOH: >> --- bash-4.2/redir.c >> +++ bash-4.2/redir.c >> @@ -632,7 +632,9 @@ >> } >>else >> { >> - fd = open (filename, flags, mode); >> + do { >> + fd = open (filename, f

Re: interrupted system call when using named pipes on FreeBSD

2013-01-30 Thread Chet Ramey
> a simple patch to workaround/fix the issue by Yuta SATOH: > --- bash-4.2/redir.c > +++ bash-4.2/redir.c > @@ -632,7 +632,9 @@ > } >else > { > - fd = open (filename, flags, mode); > + do { > + fd = open (filename, flags, mode); > + } while ((fd < 0) && (errno == EI

Re: interrupted system call when using named pipes on FreeBSD

2013-01-30 Thread Lionel Cons
On 18 January 2013 13:55, Chet Ramey wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 1/18/13 1:30 AM, Mike Frysinger wrote: >> this is somewhat a continuation of this thread: >> http://lists.gnu.org/archive/html/bug-bash/2008-10/msg00091.html >> >> i've gotten more or less the same

Re: interrupted system call when using named pipes on FreeBSD

2013-01-30 Thread Roman Rakus
On 01/30/2013 10:06 AM, Roman Rakus wrote: There is similar problem with ioctl() syscall in read. Consider following script: #!/bin/bash ( while :; do kill -CHLD $$ 2>&- || break; done ) & while :; do read -p 1 -t 0.01 -d ' ' done On my Fedora it is reporting many /tmp/test.sh: line 4:

Re: interrupted system call when using named pipes on FreeBSD

2013-01-30 Thread Roman Rakus
On 01/29/2013 10:59 PM, Chet Ramey wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/18/13 1:30 AM, Mike Frysinger wrote: this is somewhat a continuation of this thread: http://lists.gnu.org/archive/html/bug-bash/2008-10/msg00091.html i've gotten more or less the same report in Gentoo:

Re: interrupted system call when using named pipes on FreeBSD

2013-01-29 Thread Chet Ramey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/18/13 1:30 AM, Mike Frysinger wrote: > this is somewhat a continuation of this thread: > http://lists.gnu.org/archive/html/bug-bash/2008-10/msg00091.html > > i've gotten more or less the same report in Gentoo: > http://bugs.gentoo.org/447810 > >

Re: interrupted system call when using named pipes on FreeBSD

2013-01-18 Thread Chet Ramey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/18/13 1:45 PM, Mike Frysinger wrote: > On Friday 18 January 2013 07:55:00 Chet Ramey wrote: >> On 1/18/13 1:30 AM, Mike Frysinger wrote: >>> this is somewhat a continuation of this thread: >>> http://lists.gnu.org/archive/html/bug-bash/2008-10/msg

Re: interrupted system call when using named pipes on FreeBSD

2013-01-18 Thread Mike Frysinger
On Friday 18 January 2013 07:55:00 Chet Ramey wrote: > On 1/18/13 1:30 AM, Mike Frysinger wrote: > > this is somewhat a continuation of this thread: > > http://lists.gnu.org/archive/html/bug-bash/2008-10/msg00091.html > > > > i've gotten more or less the same report in Gentoo: > > http://bugs.gent

Re: interrupted system call when using named pipes on FreeBSD

2013-01-18 Thread Chet Ramey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/18/13 1:30 AM, Mike Frysinger wrote: > this is somewhat a continuation of this thread: > http://lists.gnu.org/archive/html/bug-bash/2008-10/msg00091.html > > i've gotten more or less the same report in Gentoo: > http://bugs.gentoo.org/447810 > >

interrupted system call when using named pipes on FreeBSD

2013-01-17 Thread Mike Frysinger
this is somewhat a continuation of this thread: http://lists.gnu.org/archive/html/bug-bash/2008-10/msg00091.html i've gotten more or less the same report in Gentoo: http://bugs.gentoo.org/447810 the simple test case is: $ cat test.sh #!/bin/bash while :; do (:)& (:)& (:)& (:)& (:)& (:)& (