From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: James Boulton <james.boulton@eiconic.com>
Cc: gdb@sourceware.org
Subject: Re: GDB Darwin
Date: Mon, 06 Jun 2011 21:28:00 -0000 [thread overview]
Message-ID: <1307395697.2518.2.camel@hactar> (raw)
In-Reply-To: <96BD89A1BBC34A768C4DF86BDFD7FCC2@eiconicjames>
On Thu, 2011-06-02 at 14:02 +0100, James Boulton wrote:
> How do you actually go about implementing a new target? Most of the
> functionality is present (mach-o, arm, darwin) but it needs glueing together
> correctly.
You may find this document useful:
http://www.embecosm.com/appnotes/ean3/embecosm-howto-gdb-porting-ean3-issue-2.html
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
prev parent reply other threads:[~2011-06-06 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTikpEhjP-RPyLFcwoF=nC3K+oas-ZQ@mail.gmail.com>
2011-04-13 13:33 ` Follow-fork-mode and inferiors Kevin Pouget
2011-04-13 14:29 ` Tom Tromey
2011-04-13 14:50 ` Kevin Pouget
2011-06-01 15:29 ` Pedro Alves
2011-06-01 15:51 ` GDB Darwin James Boulton
2011-06-01 16:22 ` Joel Brobecker
2011-06-02 13:03 ` James Boulton
2011-06-06 21:28 ` Thiago Jung Bauermann [this message]
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=1307395697.2518.2.camel@hactar \
--to=bauerman@br.ibm.com \
--cc=gdb@sourceware.org \
--cc=james.boulton@eiconic.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).