Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: gdb@sourceware.org
Subject: Re: expected behavior when a signal is sent to the ptraced child
Date: Thu, 25 May 2006 09:06:00 -0000	[thread overview]
Message-ID: <20060525032939.GA18883@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0605251036160.2738@localhost.localdomain>

On Thu, May 25, 2006 at 10:36:37AM +0800, Wu Zhou wrote:
> It will stop instead. then the wait function of the prarent (in our case, 
> GDB) will return and get the control. It can inspect the status of the 
> child and know what cause the child to stop.  Then gdb can let the child
> continue using PTRACE_CONT, in this it can choose to delieve the signal on 
> to the child, and also ignore it, and even deliver a different signal.

Yes.

> If my understanding is correct. Then a follow up question is how to make 
> the child not to call its signal handler and to stop instead.  The reason 
> I ask this is that with one kernel, I get different result than the above
> with the following test code:

If the child receives a signal, it will stop.  It looks to me as if
your kernel is not generating the signal in the normal way, i.e.
somehow bypassing normal delivery.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-05-25  3:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-25  4:16 Wu Zhou
2006-05-25  9:06 ` Daniel Jacobowitz [this message]
2006-05-25 12:07   ` Wu Zhou
2006-05-25 13:06 ` Andreas Schwab
2006-05-25 19:37   ` Daniel Jacobowitz
2006-05-26 20:57     ` Wu Zhou
2006-05-25 13:47 Wu Zhou
2006-05-26  2:18 Wu Zhou

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=20060525032939.GA18883@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=woodzltc@cn.ibm.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