From: Daniel Jacobowitz <drow@false.org>
To: Ron McCall <ronald.mccall@snet.net>
Cc: gdb@sourceware.org
Subject: Re: Hacking gdbserver to capture instruction-level code coverage
Date: Wed, 21 Jun 2006 16:51:00 -0000 [thread overview]
Message-ID: <20060621153102.GA5320@nevyn.them.org> (raw)
In-Reply-To: <20060621152810.56441.qmail@web80332.mail.yahoo.com>
On Wed, Jun 21, 2006 at 08:28:10AM -0700, Ron McCall wrote:
> I have attempted to hack gdbserver 6.5 to log
> instruction-level code coverage on a powerpc-linux
> system and it seems to work except that examining
> variables is broken as a result. Turning on remote
> debugging in gdb and comparing a run using an
> unmodified gdbserver and the modified gdbserver seems
> to show a difference with the DBAT0 register mapping
> in the 'g' packet responses. It would seem that my
> changes have somehow violated something and perhaps
> has confused the Linux kernel?
At this point you've lost me.
The PPC 'g' packet contains r0-r31, f0-f31, pc, ps, cr, lr, ctr, xer,
and fpscr. The BAT registers aren't involved at all; I don't even
think they're usable from userspace.
> Does any of this sound particularly evil? I can
> provide the small patch against the 6.5 source if
> anyone needs to see the changes in more detail.
Evil but functional, as long as you're being careful to not lose track
of signals.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-21 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 15:31 Ron McCall
2006-06-21 16:51 ` Daniel Jacobowitz [this message]
2006-06-21 21:46 ` Ron McCall
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=20060621153102.GA5320@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=ronald.mccall@snet.net \
/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