From: Daniel Jacobowitz <dan@debian.org>
To: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Ptrace updates [0/5]
Date: Thu, 6 Feb 2003 17:39:24 -0500 [thread overview]
Message-ID: <20030206223924.GA22688@nevyn.them.org> (raw)
It's been a while since the last set of ptrace patches; here's what I've
queued up. They'll follow in individual messages, or they're available by
BitKeeper (details below).
These are all small changes; there may be some more interesting ones in a
couple of weeks, after GDB support for NPTL is more mature. Overview:
- Two new traceable events, end-of-vfork and process exit.
- Ptrace calls to get and set the siginfo struct associated with a signal.
- Two separate signal handling fixes for the fork-tracing and CLONE_PTRACE
support.
- A bugfix to prevent zombie processes when debugging LinuxThreads.
Linus, please do a
bk pull http://ptrace.bkbits.net/for-linus-2.5
This will update the following files:
include/linux/ptrace.h | 6 ++++++
include/linux/sched.h | 3 +++
kernel/exit.c | 30 ++++++++++++++++++++++++++----
kernel/fork.c | 8 +++++---
kernel/ptrace.c | 36 +++++++++++++++++++++++++++++++++++-
kernel/signal.c | 8 +++++++-
6 files changed, 82 insertions(+), 9 deletions(-)
through these ChangeSets:
<drow@nevyn.them.org> (03/02/06 1.961)
Signal handling bugs for thread exit + ptrace
<drow@nevyn.them.org> (03/02/06 1.960)
Add PTRACE_O_TRACEVFORKDONE and PTRACE_O_TRACEEXIT facilities.
<drow@nevyn.them.org> (03/02/04 1.959)
Use force_sig_specific to send SIGSTOP to newly-created CLONE_PTRACE processes.
<drow@nevyn.them.org> (03/01/18 1.958)
Add PTRACE_GETSIGINFO and PTRACE_SETSIGINFO
These new ptrace commands allow a debugger to control signals more precisely;
for instance, store a signal and deliver it later, as if it had come from the
original outside process or in response to the same faulting memory access.
<drow@nevyn.them.org> (03/01/18 1.957)
Tweak has_stopped_jobs for use with debugging
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2003-02-06 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 22:39 Daniel Jacobowitz [this message]
2003-02-06 22:40 ` Ptrace updates: has_stopped_jobs [1/5] Daniel Jacobowitz
2003-02-06 22:41 ` Ptrace updates: PTRACE_GETSIGINFO [2/5] Daniel Jacobowitz
2003-02-06 22:42 ` Ptrace updates: CLONE_PTRACE should use force_sig_specific [3/5] Daniel Jacobowitz
2003-02-06 22:42 ` Ptrace updates: event tracing for vfork finish and process exit [4/5] Daniel Jacobowitz
2003-02-06 22:43 ` Ptrace updates: Prevent zombies when debugging LinuxThreads apps [5/5] Daniel Jacobowitz
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=20030206223924.GA22688@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).