From: Luis Machado <luis.machado@arm.com>
To: Paul Koning <paulkoning@comcast.net>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>, gdb@sourceware.org
Subject: Re: GDB on M1 mac?
Date: Wed, 22 Jun 2022 14:06:10 +0100 [thread overview]
Message-ID: <ef553219-0202-e9a7-3225-51813fa103a3@arm.com> (raw)
In-Reply-To: <AD6ECC78-27FC-4172-9107-BEB3DAB07AB4@comcast.net>
On 6/22/22 14:01, Paul Koning wrote:
>
>
>> On Jun 22, 2022, at 4:57 AM, Luis Machado via Gdb <gdb@sourceware.org> wrote:
>>
>> Hi,
>>
>> On 6/22/22 07:52, Gerd Möllmann via Gdb wrote:
>>> I tried bulding gdb 12.1 on macOS 12.4 with an Apple M1 chip, but it öooks like that target is not supported.
>>> Can I ask if there are plans to support that platform, or even work in progress that I could try out? (I'd use it for debugging Emacs on macOS.)
>>> TIA
>>
>> Arm has macOS-hosted arm-none-eabi tools, but I don't think native aarch64 debugging on macOS is supported, as you said.
>>
>> I can't speak for other contributors, but I don't know of any plan to support that OS/arch combination for GDB. We're open to
>> accepting patches though.
>>
>> I think LLDB is the way to go on macOS.
>
> Unfortunately that seems to be the only option right now, but it's a nasty one. The UI is obnoxious, and it can't debug GCC output at all unless it was compiled with -O0.
Technically we have darwin native support for x86-64 (don't know how well it works). If that works well, It might be a matter of implementing the native parts for aarch64.
next prev parent reply other threads:[~2022-06-22 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aae73c66-2cd0-4710-b9ad-ac1f2770b08d@Spark>
2022-06-22 6:52 ` Gerd Möllmann
2022-06-22 8:57 ` Luis Machado
2022-06-22 13:01 ` Paul Koning
2022-06-22 13:06 ` Luis Machado [this message]
2022-06-22 13:09 ` Paul Koning
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=ef553219-0202-e9a7-3225-51813fa103a3@arm.com \
--to=luis.machado@arm.com \
--cc=gdb@sourceware.org \
--cc=gerd.moellmann@gmail.com \
--cc=paulkoning@comcast.net \
/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).