From: James Sampson <i_am_triumph@ofir.dk>
To: Andrew Cagney <ac131313@redhat.com>
Cc: GDB Archive <gdb@sources.redhat.com>
Subject: RE: Porting GDB - Where to start?
Date: Tue, 26 Nov 2002 00:15:00 -0000 [thread overview]
Message-ID: <20021126084143.87BD12D6E9@postfix2.ofir.com> (raw)
>> It's an ELF port, but xstormy16 is still probably your best bet.
>
>Yes.
>
>(GDB ports are object file netural. Handling elf, xcoff, coff, ... is a
>bfd problem and as long as BFD can handle it, so can GDB. The only
>potential got-ya is the debug info, use GCC and you should be safe >there.)
Ok then :-)
A couple of questions:
1. Why is xstormy16 the best place to start?.
2. Since I can't use GCC to make target specific code for a C55x I must use
CCS (Code Composer Studio) from TI. What could a "got-ya" be?.
Best Regards
James
next reply other threads:[~2002-11-26 8:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 0:15 James Sampson [this message]
2002-11-26 7:01 ` Andrew Cagney
2002-12-03 22:48 ` Jim Blandy
-- strict thread matches above, loose matches on Subject: below --
2002-11-26 7:53 James Sampson
2002-12-01 13:18 ` Daniel Jacobowitz
2002-12-01 22:16 ` Eli Zaretskii
2002-12-02 6:28 ` Daniel Jacobowitz
2002-12-02 11:14 ` Eli Zaretskii
2002-11-25 1:56 James Sampson
2002-11-25 6:29 ` Daniel Jacobowitz
2002-11-25 10:22 ` 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=20021126084143.87BD12D6E9@postfix2.ofir.com \
--to=i_am_triumph@ofir.dk \
--cc=ac131313@redhat.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