Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb@sources.redhat.com
Subject: Re: SIGCHLD ignored
Date: Wed, 11 Jun 2008 18:09:00 -0000	[thread overview]
Message-ID: <g2p4bb$vc8$1@ger.gmane.org> (raw)
In-Reply-To: <20080611173626.GA25045@caradoc.them.org>

Daniel Jacobowitz wrote:

> On Wed, Jun 11, 2008 at 09:21:05PM +0400, Vladimir Prus wrote:
>> 
>> A fellow KDevelop hacker has reported that when running kdevelop itself
>> under CVS HEAD of gdb, kdevelop hangs. What happens if that kdevelop spawns
>> subprocess, and then does not notice it has exited, because it never
>> receives SIGCHLD. I attach a much reduced project that requires only Qt4,
>> and probably an even more reduced project is possible.
>> 
>> If I apply the attached patch to GDB, things work fine -- but I suspect
>> this 'fix' will break something else.
>> 
>> Pedro, I think this SIGCHLD magic is your doing -- do you have any ideas
>> how to fix it?
> 
> linux_nat_create_inferior is already unblocking signals before
> creating.  Does normal_mask contain SIGCHLD? 

It does not, at least when the normal_mask is initially obtained.
linux_nat_create_inferior does restore the mask. Still, my test
case does not work.

> The approach taken (search for "signal" in fork-child.c, first
> comment) may not be compatible with async...

I actually would appreciate some comments about what we do with SIGCHLD
in linux-nat.c -- the code is fairly complex to understand this by
reading.

- Volodya





  reply	other threads:[~2008-06-11 18:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11 17:21 Vladimir Prus
2008-06-11 17:36 ` Daniel Jacobowitz
2008-06-11 18:09   ` Vladimir Prus [this message]
2008-06-11 18:42     ` Michael Snyder
2008-06-11 22:45 ` Pedro Alves
2008-06-11 23:20   ` Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='g2p4bb$vc8$1@ger.gmane.org' \
    --to=vladimir@codesourcery.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox