From: Daniel Jacobowitz <drow@false.org>
To: "Rick.Lee" <rickmaillist@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: gdb over smbus
Date: Mon, 09 Jul 2007 11:40:00 -0000 [thread overview]
Message-ID: <20070709114050.GA3095@caradoc.them.org> (raw)
In-Reply-To: <ee979a50707090143y5c2d453fj5b080b7d078392c6@mail.gmail.com>
On Mon, Jul 09, 2007 at 04:43:42PM +0800, Rick.Lee wrote:
> thanks,Daniel,
> there are some incorrect information about this soc, through
> smbus interface, cpu core registers, such as status register, register
> files r0-rx could not be accessed, all other peripheral registers can
> be accessed,including breakpoint enable/disable.
> with these restrictions, is it still possible to do such a
> converter to support source level debuging?
You will have to come up with some way to access the core registers,
if you expect GDB to know the current PC.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-07-09 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 8:21 Rick.Lee
2007-07-06 11:59 ` Daniel Jacobowitz
2007-07-09 8:44 ` Rick.Lee
2007-07-09 11:40 ` Daniel Jacobowitz [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=20070709114050.GA3095@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=rickmaillist@gmail.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