From: Daniel Jacobowitz <drow@false.org>
To: Kim Lux <lux@diesel-research.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb for multicore processors ?
Date: Thu, 08 Dec 2005 13:56:00 -0000 [thread overview]
Message-ID: <20051208135600.GA20771@nevyn.them.org> (raw)
In-Reply-To: <1134020979.27506.23.camel@localhost.localdomain>
On Wed, Dec 07, 2005 at 10:49:39PM -0700, Kim Lux wrote:
> One more thing.
>
> XGate code gets compiled to reside in flash. However, it gets relocated
> to run from RAM as it runs much faster there. GDB will have to know
> that the address it sees in RAM isn't the address it was compiled to.
> The file format is elf, if that helps.
How to handle this depends on how you do it. Traditionally you set the
VMA in the ELF file to point to the RAM location; then everything will
Just Work.
> On Wed, 2005-12-07 at 22:47 -0700, Kim Lux wrote:
> > Each processor has its own register set and instruction set. They are
> > not the same. They share the same memory map, but the xgate processor
> > addresses things differently.
> > We are building the BDM, so theoretically we could connect 2 gdb
> > processes to the same BDM, if that helps. That would allow us to have a
> > separate GDB instance for each process. Or should one GDB instance
> > handle both processors ?
I strongly recommend using two GDB sessions, for now. It's a long-term
design goal for GDB to be able to debug heterogenous systems, but no
one has been working on it lately, and there's a long way to go.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-12-08 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 5:47 Kim Lux
2005-12-08 5:49 ` Kim Lux
2005-12-08 13:56 ` Daniel Jacobowitz [this message]
2006-09-29 3:30 gdb for multicore processors? Bridge Wu
2006-09-29 18:10 ` Michael Snyder
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=20051208135600.GA20771@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=lux@diesel-research.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