From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: GDB paper accepted for GCC summit
Date: Thu, 30 Mar 2006 04:13:00 -0000 [thread overview]
Message-ID: <20060330013607.GA17383@nevyn.them.org> (raw)
In-Reply-To: <e0fc4m$91b$1@sea.gmane.org>
On Thu, Mar 30, 2006 at 09:26:53AM +0800, Randolph Chung wrote:
> This is my understanding:
> multi-arch is a generalized form of biarch, the idea being that one gdb
> binary can debug multiple targets. The most common form of this is a gdb
> that can debug 32-bit and 64-bit binaries on the same machine, but
> presumably one could build a gdb that can debug e.g. x86 targets
> natively, and at the same time an embedded arm target. I don't know if
> we are quite there yet though. Most of this work involves encapsulating
> target specific operations into vectors that can be changed at runtime,
> instead of having link-time bindings of those operations.
Yes. We're very close; if someone wanted to make this work, they
probably could. IIRC it once worked for a couple of embedded targets.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-30 1:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-18 11:13 PAUL GILLIAM
2006-03-19 17:05 ` Eli Zaretskii
2006-03-30 0:32 ` PAUL GILLIAM
2006-03-30 1:41 ` Randolph Chung
2006-03-30 4:13 ` Daniel Jacobowitz [this message]
2006-03-30 22:42 ` Mark Kettenis
2006-03-30 1:36 ` GDB paper for GCC summit: New Commands PAUL GILLIAM
2006-03-30 4:30 ` Joel Brobecker
2006-04-01 13:21 ` Eli Zaretskii
2006-04-10 22:27 ` GDB paper at GCC summit: user-level features PAUL GILLIAM
2006-04-11 9:01 ` GDB paper accepted for GCC summit PAUL GILLIAM
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=20060330013607.GA17383@nevyn.them.org \
--to=drow@false.org \
--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