From: Daniel Jacobowitz <drow@false.org>
To: Duane Ellis <duane@duaneellis.com>
Cc: gdb@sourceware.org
Subject: Re: GDB for multiple targets
Date: Mon, 24 Nov 2008 22:03:00 -0000 [thread overview]
Message-ID: <20081124220204.GA8666@caradoc.them.org> (raw)
In-Reply-To: <492AD78E.4040905@duaneellis.com>
On Mon, Nov 24, 2008 at 11:34:22AM -0500, Duane Ellis wrote:
> Are you describing additional items in "target.xml" that GDB requests
> from the remote?
Right.
> If so - what about other items, such as target endian, cputype (or in arm
> terms, "arch") and perhaps a flag that indicates the target is "bare
> metal" and not an operating system based target?
We can add pretty much anything there that is useful. Architecture is
already supported (<architecture>), or is that not sufficient? The
OSABI setting that Ulrich is referring to covers the bare metal / OS
distinction, too.
Endianness is not currently present but would be an easy addition.
I haven't bothered, because in most cases you have an executable file;
that doesn't tell you the CPU arch, but it does tell you the
endianness.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-11-24 22:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 16:36 Duane Ellis
2008-11-24 22:03 ` Daniel Jacobowitz [this message]
2008-11-25 0:04 ` Duane Ellis
2008-11-25 4:06 ` Daniel Jacobowitz
2008-11-25 17:48 ` Duane Ellis
2008-11-26 2:51 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2008-11-21 17:09 Marc Khouzam
2008-11-21 19:07 ` Michael Snyder
2008-11-22 15:26 ` Ulrich Weigand
2008-12-09 14:42 ` Marc Khouzam
2008-12-09 18:12 ` Ulrich Weigand
2008-12-09 18:40 ` Marc Khouzam
2008-12-09 18:44 ` Ulrich Weigand
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=20081124220204.GA8666@caradoc.them.org \
--to=drow@false.org \
--cc=duane@duaneellis.com \
--cc=gdb@sourceware.org \
/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