This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug dyninst/16250] New: Allow triggering remote gdb through stapdyn
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Mon, 25 Nov 2013 22:40:07 +0000
- Subject: [Bug dyninst/16250] New: Allow triggering remote gdb through stapdyn
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=16250
Bug ID: 16250
Summary: Allow triggering remote gdb through stapdyn
Product: systemtap
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: dyninst
Assignee: systemtap at sourceware dot org
Reporter: jistone at redhat dot com
Like Valgrind's "gdbserver" functionality, it would be nice if a stap script
could trigger gdb on a target process. I imagine this will be best approached
in stapdyn mode, but maybe it could be considered from the kernel runtime too.
I expect two main tasks required:
1. Create the actual gdbserver / gdb stub. Since Dyninst already has ptrace
control of its process in libpcontrol.so, this might make the most sense as a
new feature of proccontrol. This will surely involve the most effort.
2. Create the trigger for scripts, probably just as a tapset function. It
needs to be a synchronous event which freezes the process until gdb arrives.
Whether the probe completes first is up for debate. It only makes sense to be
called from within a target process, not from stapdyn itself in
begin/end/timer/etc.
--
You are receiving this mail because:
You are the assignee for the bug.