linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Christopher R. Johnson" <cjohnson@gcctech.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: powerpc gdb and gdbserver
Date: Thu, 18 Dec 2003 12:10:10 -0500	[thread overview]
Message-ID: <20031218171010.GA16791@nevyn.them.org> (raw)
In-Reply-To: <3FE0977B.7020504@gcctech.com>


On Wed, Dec 17, 2003 at 12:50:51PM -0500, Christopher R. Johnson wrote:
>
> I'm about to go and grab gdb to build a host-based debugger and
> target-based (PPC 405GP) gdbserver.  Anybody out there with advice on
> how to do this?  Should it just work out of the box or is there stuff I
> need to do to gdbserver for this platform?  The sources I just found are
> gdb-6.0, and I'm using quite recent tools (gcc 3.3.2 glibc 2.3.2
> binutils 2.14.90.0.5 - kudos to Dan Kegle for the crosstools stuff!!!).
>
> Thanks!

It should simply build and work.  You build GDB by setting a --target
and gdbserver by setting a --host.  If you don't want to build a native
GDB at the same time, run the --host build by gdbserver/configure
instead of the top-level src/configure.

--
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-12-18 17:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-17 17:50 powerpc gdb and gdbserver Christopher R. Johnson
2003-12-18 17:10 ` Daniel Jacobowitz [this message]
2003-12-18 20:27   ` Christopher R. Johnson
2003-12-18 20:35     ` Daniel Jacobowitz
2003-12-18 20:37       ` Christopher R. Johnson
2003-12-19 20:35         ` Wolfgang Denk
2003-12-22  3:52         ` Daniel Jacobowitz
2003-12-22 15:32           ` Christopher R. Johnson
2003-12-19  9:37   ` Marius Groeger
2003-12-22  3:52     ` Daniel Jacobowitz

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=20031218171010.GA16791@nevyn.them.org \
    --to=drow@false.org \
    --cc=cjohnson@gcctech.com \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).