From: LaPonsey Brian-ra4951 <Brian.Laponsey@motorola.com>
Cc: gdb-patches@sources.redhat.com
Subject: RE: mcore registers
Date: Tue, 30 Sep 2003 15:22:00 -0000 [thread overview]
Message-ID: <15BB35FC418BD511868500D0B7B916B108A3501B@zuk07exm02.sps.mot.com> (raw)
> Ok. Note that GDB doesn't run length encode. Instead it
Oh. I was depending on the manual being right - I didn't know the RLE feature was non-functional. You just saved me having to find that out the hard way.
> tries to use
> the "P" packet. If not already, also look at the "T..." response to
> things like continue.
Right, I could recode the T packet responses so that they don't just cycle through all the regs. The reg number is encoded in there, so I could skip over the non-existent ones.
Not familiar with the P packet. Back to the fine manual.
Brian
next reply other threads:[~2003-09-30 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 15:22 LaPonsey Brian-ra4951 [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-30 8:21 LaPonsey Brian-ra4951
2003-09-30 14:46 ` Andrew Cagney
2003-09-30 15:34 ` Paul Koning
2003-09-30 15:40 ` Andrew Cagney
2003-09-29 15:17 LaPonsey Brian-ra4951
2003-09-29 17:25 ` Andrew Cagney
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=15BB35FC418BD511868500D0B7B916B108A3501B@zuk07exm02.sps.mot.com \
--to=brian.laponsey@motorola.com \
--cc=gdb-patches@sources.redhat.com \
/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