Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Tom de Vries <tdevries@suse.de>,
	Abhay Kandpal <abhay@linux.ibm.com>,
	Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/2] Fix regressions after find_function_in_inferior changes
Date: Thu, 10 Sep 2026 14:13:51 +0100	[thread overview]
Message-ID: <cover.1789034019.git.aburgess@redhat.com> (raw)

After commit:

  commit 32090b27e92cb8fd4998e8e8e65d43f445545bc7
  Date:   Wed Sep 2 10:43:34 2026 +0100

      gdb: fix incorrect search domain in find_function_in_inferior

Bug PR gdb/34602 was created which details some new regressions that
were introduced for the tests:

  gdb.ada/funcall_ref.exp
  gdb.ada/arrayparam.exp
  gdb.compile/compile.exp
  gdb.compile/compile-cplus.exp

This series fixes these regressions.  The gdb.compile/ tests are fixed
by the first patch and the gdb.ada/ tests by the second.

Thanks,
Andrew

---

Andrew Burgess (2):
  gdb: fill in default return types for some inferior function calls
  gdb: catch some exceptions in find_function_in_inferior

 gdb/gcore.c      |  4 +++-
 gdb/linux-fork.c | 13 +++++++++++--
 gdb/linux-tdep.c |  8 ++++++--
 gdb/valops.c     | 35 +++++++++++++++++++++++++----------
 4 files changed, 45 insertions(+), 15 deletions(-)


base-commit: e0d8f6fc3867435e37e0409987b63e70aee4513b
-- 
2.25.4


             reply	other threads:[~2026-09-10 13:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10 13:13 Andrew Burgess [this message]
2026-09-10 13:13 ` [PATCH 1/2] gdb: fill in default return types for some inferior function calls Andrew Burgess
2026-09-11 14:38   ` Tom Tromey
2026-09-10 13:13 ` [PATCH 2/2] gdb: catch some exceptions in find_function_in_inferior Andrew Burgess
2026-09-11 11:07   ` Tom de Vries
2026-09-11 14:42     ` Tom Tromey
2026-09-11 14:43 ` [PATCH 0/2] Fix regressions after find_function_in_inferior changes 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=cover.1789034019.git.aburgess@redhat.com \
    --to=aburgess@redhat.com \
    --cc=abhay@linux.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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