From: "Jérôme Duval" <jerome.duval@gmail.com>
To: gdb-patches@sourceware.org
Cc: "Jérôme Duval" <jerome.duval@gmail.com>
Subject: [PATCH 7/8] gdb: Update Haiku support for 18.x
Date: Thu, 12 Mar 2026 18:23:35 +0100 [thread overview]
Message-ID: <20260312172336.15450-8-jerome.duval@gmail.com> (raw)
In-Reply-To: <20260312172336.15450-1-jerome.duval@gmail.com>
---
gdb/haiku-tdep.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gdb/haiku-tdep.c b/gdb/haiku-tdep.c
index f0fd1d2f..647e6fcc 100644
--- a/gdb/haiku-tdep.c
+++ b/gdb/haiku-tdep.c
@@ -22,6 +22,7 @@
#include "bfd.h"
#include "elf-bfd.h"
#include "gdbarch.h"
+#include "gdbcore.h"
#include "haiku-tdep.h"
#include "inferior.h"
#include "osdata.h"
@@ -71,7 +72,7 @@ haiku_bfd_open_commpage ()
Otherwise, GDB will complain with a segfault. */
bfd *tmpbfd = current_inferior ()->pspace->exec_bfd ();
if (tmpbfd == nullptr)
- tmpbfd = current_inferior ()->pspace->core_bfd ();
+ tmpbfd = get_inferior_core_bfd (current_inferior ());
if (tmpbfd == nullptr)
return nullptr;
--
2.43.0
next prev parent reply other threads:[~2026-03-12 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 17:23 [PATCH 0/8] Support for Haiku/x86-64 in GDB Jérôme Duval
2026-03-12 17:23 ` [PATCH 1/8] gdbserver: Initial Haiku support Jérôme Duval
2026-03-12 19:06 ` Kevin Buettner
2026-03-12 17:23 ` [PATCH 2/8] gdb: " Jérôme Duval
2026-03-12 18:31 ` Eli Zaretskii
2026-03-12 17:23 ` [PATCH 3/8] gdb: Update Haiku support for 16.x Jérôme Duval
2026-03-12 17:23 ` [PATCH 4/8] gdbserver: " Jérôme Duval
2026-03-12 17:23 ` [PATCH 5/8] gdb: Update Haiku support for 17.x Jérôme Duval
2026-03-12 17:58 ` Tom Tromey
2026-03-12 17:23 ` [PATCH 6/8] gdbserver: " Jérôme Duval
2026-03-12 17:23 ` Jérôme Duval [this message]
2026-03-12 17:23 ` [PATCH 8/8] gdbserver: Update Haiku support for 18.x Jérôme Duval
2026-03-12 17:37 ` [PATCH 0/8] Support for Haiku/x86-64 in GDB Tom Tromey
[not found] ` <CAPZRpdPY4Uzwu5BinMEDcU=0SQEXU0ca31-p_X_ZOJzdGcobkQ@mail.gmail.com>
2026-03-12 21:42 ` Trung Nguyen
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=20260312172336.15450-8-jerome.duval@gmail.com \
--to=jerome.duval@gmail.com \
--cc=gdb-patches@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