From: Simon Marchi <simark@simark.ca>
To: "Jérôme Duval" <jerome.duval@gmail.com>, gdb-patches@sourceware.org
Cc: me@trungnt2910.com
Subject: Re: [PATCH v4 1/2] gdbserver: Haiku support
Date: Thu, 23 Apr 2026 23:02:55 -0400 [thread overview]
Message-ID: <361cf9e6-36a4-4d90-906e-72c99b050fcd@simark.ca> (raw)
In-Reply-To: <20260423185942.7061-2-jerome.duval@gmail.com>
On 2026-04-23 14:59, Jérôme Duval wrote:
> Initial support was done by Trung Nguyen for GDB 15.1 for GSoC 2024:
> See blog entries https://www.haiku-os.org/tags/gdb
> Original Port repository: https://github.com/trungnt2910/gdb-haiku
>
> I mostly adapted to the next major releases.
Hi Jérôme,
I'm just looking at the existing modified files for now, but I'll like
to look at the whole thing eventually (it's just that the number of
lines makes it scary :)).
> diff --git a/gdbserver/Makefile.in b/gdbserver/Makefile.in
> index e45c89dc..890f05cb 100644
> --- a/gdbserver/Makefile.in
> +++ b/gdbserver/Makefile.in
> @@ -592,6 +592,12 @@ gdbreplay.o: gdbreplay.cc
> $(ECHO_CXX) $(COMPILE.pre) $(INTERNAL_CFLAGS) $(CXXFLAGS) \
> -include gdbsupport/common-defs.h $(COMPILE.post) $<
>
> +# Rule for Haiku files. This is the same as COMPILE, but does not include
> +# server.h to avoid name clashes with Haiku system structs.
> +nat/haiku-%.o: ../gdb/nat/haiku-%.c
> + $(ECHO_CXX) $(COMPILE.pre) $(INTERNAL_CFLAGS) $(CXXFLAGS) \
> + $(COMPILE.post) -x c++ $<
What are the clashes? We can always rename (or namespace) things in GDB.
That would be nicer in the long run than having special rules for Haiku.
> diff --git a/include/gdb/signals.def b/include/gdb/signals.def
> index c6819b0f..0d4bb011 100644
> --- a/include/gdb/signals.def
> +++ b/include/gdb/signals.def
> @@ -196,7 +196,9 @@ SET (GDB_EXC_BREAKPOINT, 150, "EXC_BREAKPOINT", "Breakpoint")
>
> SET (GDB_SIGNAL_LIBRT, 151, "SIGLIBRT", "librt internal signal")
>
> +SET (GDB_SIGNAL_SIGKILLTHR, 152, "SIGKILLTHR", "Thread killed")
Since this is non-standard (AFAIK), this could use a comment.
Simon
next prev parent reply other threads:[~2026-04-24 3:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 18:59 [PATCH v4 0/2] Support for Haiku/x86-64 in GDB Jérôme Duval
2026-04-23 18:59 ` [PATCH v4 1/2] gdbserver: Haiku support Jérôme Duval
2026-04-24 3:02 ` Simon Marchi [this message]
2026-04-23 18:59 ` [PATCH v4 2/2] gdb: " Jérôme Duval
2026-04-24 3:10 ` Simon Marchi
2026-04-24 3:13 ` Simon Marchi
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=361cf9e6-36a4-4d90-906e-72c99b050fcd@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=jerome.duval@gmail.com \
--cc=me@trungnt2910.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