From: Tom de Vries <tdevries@suse.de>
To: Andrew Burgess <aburgess@redhat.com>,
Abhay Kandpal <abhay@linux.ibm.com>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: fix incorrect search domain in find_function_in_inferior
Date: Tue, 8 Sep 2026 19:23:53 +0200 [thread overview]
Message-ID: <4d32c371-0fe2-4865-a6ba-0f51105e9bc8@suse.de> (raw)
In-Reply-To: <874ifzr9nc.fsf@redhat.com>
On 9/8/26 6:27 PM, Andrew Burgess wrote:
> Before then, if you wanted to test this patch, especially Tom de Vries
> for the gdb.ada/ regressions, do let me know how you get on.
Hi Andrew,
I've applied the patch, it didn't fix the regressions.
I did:
...
$ gdb -q -batch -x outputs/gdb.ada/funcall_ref/gdb.in.1
...
which reproduced the failure, and "catch throw" brought me to:
...
static const block *
ada_alias_get_block_value (const struct symbol *sym)
{
const char *name = get_imported_name (sym);
block_symbol real_symbol = lookup_global_symbol (name, nullptr,
SEARCH_TYPE_DOMAIN);
if (real_symbol.symbol == nullptr)
error (_("could not find alias '%s' for function '%ps'"),
name,
styled_string (function_name_style.style (), sym->print_name
()));
...
I reverted both patches and put a breakpoint on
ada_alias_get_block_value, but it didn't get triggered.
Thanks,
- Tom
next prev parent reply other threads:[~2026-09-08 17:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 16:16 Andrew Burgess
2026-09-03 20:23 ` Tom Tromey
2026-09-04 9:54 ` Andrew Burgess
2026-09-07 22:30 ` Tom de Vries
2026-09-08 5:52 ` Tom de Vries
2026-09-08 15:28 ` Andrew Burgess
2026-09-08 5:55 ` Abhay Kandpal
2026-09-08 16:27 ` Andrew Burgess
2026-09-08 17:23 ` Tom de Vries [this message]
2026-09-07 18:39 ` Abhay Kandpal
2026-09-08 8:05 ` Andrew Burgess
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=4d32c371-0fe2-4865-a6ba-0f51105e9bc8@suse.de \
--to=tdevries@suse.de \
--cc=abhay@linux.ibm.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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