From: Ron McCall <ronald.mccall@snet.net>
To: gdb@sourceware.org
Subject: Re: Hacking gdbserver to capture instruction-level code coverage
Date: Wed, 21 Jun 2006 21:46:00 -0000 [thread overview]
Message-ID: <20060621165120.22709.qmail@web80313.mail.yahoo.com> (raw)
In-Reply-To: <20060621153102.GA5320@nevyn.them.org>
--- Daniel Jacobowitz <drow@false.org> wrote:
> 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.
Oops, I made a mistake decoding the registers...FPRs
are 64 bits each, not 32 bits! Gotta go back and
re-examine the correctly decoded registers to see
what's different for real this time. Thanks for
pointing out that stupid error.
> Evil but functional, as long as you're being careful
> to not lose track
> of signals.
I believe I am not losing any signals except for the
intermediate SIGTRAPs resulting from repeated single
steps (all but the last one).
Ron
prev parent reply other threads:[~2006-06-21 16:51 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
2006-06-21 21:46 ` Ron McCall [this message]
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=20060621165120.22709.qmail@web80313.mail.yahoo.com \
--to=ronald.mccall@snet.net \
--cc=gdb@sourceware.org \
/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