[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-bash] Named fifo's causing hanging bash scripts
From: |
Dr. Werner Fink |
Subject: |
Re: [bug-bash] Named fifo's causing hanging bash scripts |
Date: |
Fri, 16 Jan 2015 17:47:49 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Fri, Jan 16, 2015 at 10:46:02AM -0500, Chet Ramey wrote:
> >>
> >> What do ps and gdb tell you about pid 19175 (and the corresponding pid in
> >> the call to waitchld in the other traceback)? Running, terminated, reaped,
> >> other?
> >
> > d136:~ # ps 10942
> > PID TTY STAT TIME COMMAND
> > d136:~ #
> >
> > ... the process does not exists anymore. I guess that this could belong to
> > the sed commands of the script.
>
> This is why I need to be able to reproduce it. If the process got reaped,
> when would it have happened and why would the call to wait_for() have
> found a valid CHILD struct for it? The whole loop runs with SIGCHLD
> blocked, so it's not as if the signal handler could have reaped the
> child out from under it. I have questions but no way to find answers.
OK, thanks for your effort ... I've strip the spec file down step by step and
reached success at commenting out -DMUST_UNBLOCK_CHLD=1 (mea culpa) ... many
thanks for your help!
Werner
--
"Having a smoking section in a restaurant is like having
a peeing section in a swimming pool." -- Edward Burr
signature.asc
Description: Digital signature
Re: Named fifo's causing hanging bash scripts, Chet Ramey, 2015/01/16