|| ||Daniel Jacobowitz <email@example.com>|
|| ||firstname.lastname@example.org, email@example.com|
|| ||Ptrace updates [0/5]|
|| ||Thu, 6 Feb 2003 17:39:24 -0500|
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
- 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:
<firstname.lastname@example.org> (03/02/06 1.961)
Signal handling bugs for thread exit + ptrace
<email@example.com> (03/02/06 1.960)
Add PTRACE_O_TRACEVFORKDONE and PTRACE_O_TRACEEXIT facilities.
<firstname.lastname@example.org> (03/02/04 1.959)
Use force_sig_specific to send SIGSTOP to newly-created CLONE_PTRACE processes.
<email@example.com> (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.
<firstname.lastname@example.org> (03/01/18 1.957)
Tweak has_stopped_jobs for use with debugging
MontaVista Software Debian GNU/Linux Developer
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/