From: James Sampson <i_am_triumph@ofir.dk>
To: GDB Archive <gdb@sources.redhat.com>
Cc: drow@mvista.com
Subject: RE: Adding a target at build?
Date: Wed, 20 Nov 2002 07:38:00 -0000 [thread overview]
Message-ID: <20021120151009.823032A51B@postfix2.ofir.com> (raw)
>Look in gdb/MAINTAINERS or configure.tgt.
>
>BFD, a support library, is ported to tic54x. GDB is not. You probably
>want to talk to the author of the binutils port; check
>binutils/MAINTAINERS. I bet he's got some plans for a GDB port.
Oh God! - I had no idea there was so much work in this :-(.
Well - The GDB doesn't have to run on this target, it just needs to remote
debug it - Doesn't this simplify it a bit?
>> When this is setup, and the GDB's host is different from it's >>target,
does
>> it
>> expect to debug remotely? - Obviously it can't run it on host, >>because
the
>> code is target specific?
>>
>>Either remotely, or with a built-in simulator.
>>
>> OK - Starting to make sense :-D. But how do I load the target >>specific
>>file
>> into the GDB? - Again I need to setup my target, but how?.
>
>This is why Andrew recommended cris and xstormy16. They're relatively
>new, clean ports. It's still a lot of work but basing it on one of
>those two will be simplest.
But still - A search on "cris" in the GDB source codes reveils 300 Kb of
source code, and I'm just trying to load some code into the GDB, which it must
send to my target...
Still feel like I'm missing something :-)
Best Regards
J.S.
next reply other threads:[~2002-11-20 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 7:38 James Sampson [this message]
2002-11-20 7:42 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-11-20 11:12 James Sampson
2002-11-20 3:47 James Sampson
2002-11-19 23:19 James Sampson
2002-11-20 6:17 ` Daniel Jacobowitz
2002-11-19 6:47 James Sampson
2002-11-19 9:10 ` 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=20021120151009.823032A51B@postfix2.ofir.com \
--to=i_am_triumph@ofir.dk \
--cc=drow@mvista.com \
--cc=gdb@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