From: "James Boulton" <james.boulton@eiconic.com>
To: <gdb@sourceware.org>
Subject: Re: GDB Darwin
Date: Thu, 02 Jun 2011 13:03:00 -0000 [thread overview]
Message-ID: <96BD89A1BBC34A768C4DF86BDFD7FCC2@eiconicjames> (raw)
In-Reply-To: <20110601162203.GC2452@adacore.com>
Are there any docs on where to start with something like this?
The BFD settings from Apples branch are all present in GDB 7.2 i.e.
arm-*-darwin* | arm-*-macos10*)
targ_defvec=mach_o_le_vec
targ_selvecs="mach_o_be_vec mach_o_le_vec mach_o_fat_vec "
targ_archs="bfd_arm_arch"
targ_underscore=yes
;;
However building with that doesnt do anything useful.
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.
Thanks,
-- James
----- Original Message -----
From: "Joel Brobecker" <brobecker@adacore.com>
To: "James Boulton" <james.boulton@eiconic.com>
Cc: <gdb@sourceware.org>
Sent: Wednesday, June 01, 2011 5:22 PM
Subject: Re: GDB Darwin
>> I see GDB now has support for i386, x64 and PowerPC flavours of
>> darwin, but not ARM. Is ARM Darwin support planned? I'm trying to
>> find a nice way of debugging directly from a Windows machine (there
>> is already an ARM Darwin targeted GDB, but this is only on OSX).
>
> As far as I know, I haven't heard of anyone planning on doing the work
> for ARM.
>
> --
> Joel
>
next prev parent reply other threads:[~2011-06-02 13:03 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 [this message]
2011-06-06 21:28 ` Thiago Jung Bauermann
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=96BD89A1BBC34A768C4DF86BDFD7FCC2@eiconicjames \
--to=james.boulton@eiconic.com \
--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