From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFC] PTRACE_ATTACH problem on new Linux kernels
Date: Wed, 19 Feb 2003 17:19:00 -0000 [thread overview]
Message-ID: <3E53BDD0.70601@redhat.com> (raw)
In-Reply-To: <20030218031431.GA31807@nevyn.them.org>
> But Roland made a very convincing case for this new behavior; for
> programs like strace which just pass all signals through, this prevents
> SIGSTOPs being silently cancelled, which is a definite plus.
Er, humor me. Does it work?
GDB's problem was that it would pass down the sigstop and then promptly
get it back again (via wait?). Wouldn't strace suffer the same problem?
Unless the sigstop really is delivered that is.
Andrew
next prev parent reply other threads:[~2003-02-19 17:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 0:53 Elena Zannoni
2003-02-18 2:39 ` Andrew Cagney
2003-02-18 3:14 ` Daniel Jacobowitz
2003-02-18 3:32 ` Elena Zannoni
2003-02-19 17:19 ` Andrew Cagney [this message]
2003-02-19 17:28 ` Daniel Jacobowitz
2003-02-18 3:28 ` Elena Zannoni
2003-02-18 20:06 ` Andrew Cagney
2003-02-18 20:43 ` Elena Zannoni
2003-02-19 17:16 ` Andrew Cagney
2003-02-19 17:40 ` Kevin Buettner
2003-04-08 18:53 ` Elena Zannoni
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=3E53BDD0.70601@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@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