public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Andrew Haley via Gdb <gdb@sourceware.org>
Cc: Paul Koning <paulkoning@comcast.net>,
	 John Baldwin <jhb@FreeBSD.org>, Andrew Haley <aph@redhat.com>
Subject: Re: GDB / AArch64 / MacOS
Date: Sun, 23 Jul 2023 13:51:50 -0600	[thread overview]
Message-ID: <87h6pu9zjd.fsf@tromey.com> (raw)
In-Reply-To: <b31b882c-1afe-3a13-03d2-da241db54f52@redhat.com> (Andrew Haley via Gdb's message of "Wed, 19 Jul 2023 20:02:40 +0100")

Andrew> Maybe I could start with the AArch64/BSD target, do you think? The
Andrew> differences would be the way that args are passed between functions
Andrew> and stack layouts, I guess.

There's two parts to a gdb port like this.

One is the "tdep" code.  This holds target- and arch-dependent
information.  This is where you'd put things like knowledge of the ABI.

There's also the "nat" code.  This is host dependent code that knows how
to do low-level debugging.  E.g., linux-nat handles calling ptrace.

The split is done so cross debugging can work -- the tdep code can be
built anywhere and be used for remote debugging.  These days the nat
code tends to be shared somewhat with gdbserver, though I don't think
that was ever ported to Darwin.

For a new Darwin port you will probably need both of these.

Tom

      parent reply	other threads:[~2023-07-23 19:51 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
2023-07-20  8:50         ` Andrew Haley
2023-07-23 19:51       ` Tom Tromey [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=87h6pu9zjd.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=aph@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=jhb@FreeBSD.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).