This is the mail archive of the
mailing list for the Archer project.
Re: gdbstub initial code, v11
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Oleg Nesterov <oleg at redhat dot com>
- Cc: archer at sourceware dot org, utrace-devel at redhat dot com
- Date: Wed, 22 Sep 2010 18:06:05 -0400
- Subject: Re: gdbstub initial code, v11
- References: <20100922022226.GA27400@redhat.com>
> [...] Honestly, I don't really know how do the "right thing" here.
> Anyway, most probably this code will be changed. Like ptrace, ugdb
> uses ->report_syscall_exit() to synthesize a trap. Unlike ptrace,
> ugdb_report_signal() doesn't send SIGTRAP to itself but reports
> SIGTRAP using siginfo_t we have. In any case, whatever we do,
> multiple tracers can confuse each other.
(It seems to me that a pure gdb report, without a synthetic
self-injected SIGTRAP, should be fine.)
> Next: fully implement g/G/p/P, currently I am a bit confused...
> But what about features? [...]
You could dig out the old "fishing plan". One demonstrated
improvement was from simulating (software) watchpoints within the
gdb stub, instead of having gdb fall back to issing countless
single-steps with memory-fetch inquiries in between.