From: John Baldwin <jhb@FreeBSD.org>
To: Andrew Haley <aph@redhat.com>, Paul Koning <paulkoning@comcast.net>
Cc: gdb@sourceware.org
Subject: Re: GDB / AArch64 / MacOS
Date: Wed, 19 Jul 2023 12:29:56 -0700 [thread overview]
Message-ID: <b94a56cd-fc77-f79a-4a37-6b2eca7ec7a4@FreeBSD.org> (raw)
In-Reply-To: <b31b882c-1afe-3a13-03d2-da241db54f52@redhat.com>
On 7/19/23 12:02 PM, Andrew Haley wrote:
> On 7/19/23 18:05, Paul Koning wrote:
>>
>>> On Jul 19, 2023, at 1:02 PM, John Baldwin <jhb@FreeBSD.org> wrote:
>>>
>>> On 7/19/23 6:19 AM, Andrew Haley via Gdb wrote:
>>>> What is the status of this combo? It seems that GDB works fine for a compiled
>>>> (emulated in Rosetta) MacOS/x86 app, but not a MacOS/AArch64 app. Has anyone
>>>> seen patches to make this work?
>>>
>>> I don't think there is any support for MacOS/AArch64 as a target (e.g. no
>>> aarch64-darwin-nat.c) and I haven't seen any patches for that either.
>
> Maybe I could start with the AArch64/BSD target, do you think? The
> differences would be the way that args are passed between functions
> and stack layouts, I guess.
I think you are probably better off starting with the x86 darwin target
since it uses Mach ports for debugging rather than ptrace. Probably the
architecture-specific parts you would need (dealing with different register
sets, etc.) is fairly small.
--
John Baldwin
next prev parent reply other threads:[~2023-07-19 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 13:19 Andrew Haley
2023-07-19 17:02 ` John Baldwin
2023-07-19 17:05 ` Paul Koning
2023-07-19 19:02 ` Andrew Haley
2023-07-19 19:29 ` John Baldwin [this message]
2023-07-20 8:50 ` Andrew Haley
2023-07-23 19:51 ` Tom Tromey
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=b94a56cd-fc77-f79a-4a37-6b2eca7ec7a4@FreeBSD.org \
--to=jhb@freebsd.org \
--cc=aph@redhat.com \
--cc=gdb@sourceware.org \
--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).