From: Daniel Jacobowitz <drow@false.org>
To: Tim Harvey <tim_harvey@yahoo.com>
Cc: gdb@sources.redhat.com
Subject: Re: howto build gdb / gdbserver for x86 host with arm-linux target?
Date: Sat, 12 Feb 2005 02:53:00 -0000 [thread overview]
Message-ID: <20050211183722.GA2123@nevyn.them.org> (raw)
In-Reply-To: <20050211183441.98256.qmail@web30502.mail.mud.yahoo.com>
On Fri, Feb 11, 2005 at 10:34:41AM -0800, Tim Harvey wrote:
> The way I understand it is that I have to use my arm-linux-gdb as my host gdb
> has stubs for the host architecture not the target (right?)
The "stub" in this case is gdbserver - the name's historic. Your host
GDB is configured for your host architecture, and to use a remote stub
the GDB client has to be configured for the same architecture as the
stub. So, basically right.
> Thanks for your help!
No problem.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-02-11 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050211024733.30134.qmail@web30706.mail.mud.yahoo.com>
2005-02-11 4:28 ` Tim Harvey
2005-02-11 5:30 ` Daniel Jacobowitz
2005-02-11 14:10 ` Tim Harvey
2005-02-11 15:45 ` Daniel Jacobowitz
2005-02-11 18:37 ` Tim Harvey
2005-02-12 2:53 ` Daniel Jacobowitz [this message]
2005-02-11 4:04 Tim Harvey
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=20050211183722.GA2123@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=tim_harvey@yahoo.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