From: Randolph Chung <tausq@debian.org>
To: gdb@sources.redhat.com
Subject: Re: GDB paper accepted for GCC summit
Date: Thu, 30 Mar 2006 01:41:00 -0000 [thread overview]
Message-ID: <e0fc4m$91b$1@sea.gmane.org> (raw)
In-Reply-To: <1143675770.21920.421.camel@dufur.beaverton.ibm.com>
> Removed configureations
> HP/PA running BSD 6.1
Since its removal, this configuration has been reintroduced. Mark
maintains this IIRC.
> 5) What is 'multi-arch'? The 'set processor command can be used with
> PowerPC and the PowerPC 64-bit GDB can debug 64-bit or 32-bit
> targets. (I have heard the latter refereed to as 'bi-arch').
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.
randolph
next prev parent reply other threads:[~2006-03-30 1:27 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 [this message]
2006-03-30 4:13 ` Daniel Jacobowitz
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='e0fc4m$91b$1@sea.gmane.org' \
--to=tausq@debian.org \
--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