[Bug ada/32766] Remove need to reconstruct Ada linkage names
cvs-commit at gcc dot gnu.org
sourceware-bugzilla@sourceware.org
Wed Sep 10 22:17:25 GMT 2025
https://sourceware.org/bugzilla/show_bug.cgi?id=32766
--- Comment #2 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=27de7d7bc3c16137f03a5be2d5da2b7687200eff
commit 27de7d7bc3c16137f03a5be2d5da2b7687200eff
Author: Tom Tromey <tom@tromey.com>
Date: Mon Mar 10 15:52:17 2025 -0600
Add another minor hack to cooked_index_entry::full_name
This patch adds another minor hack to cooked_index_entry::full_name.
In particular, if GNAT emits non-hierarchical names (still the default
as the hierarchical series is blocked on one tricky problem), then a
request to compute the "linkage-style" name will now just return the
'name' field.
Without this tweak, this series would regress ada-cold-name.exp,
because the search would look for "name.cold" but the index would
return "name[cold]" as the "linkage" name (which would be wrong).
This area is a bit difficult to unravel. The best plan here, IMO, is
to change Ada to work like the other languages in gdb: store the
natural name and do searches with that name. I think this is
achievable, but I didn't want to try it here.
I've updated the relevant bug (tagged below) to reflect this.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=32766
Acked-By: Simon Marchi <simon.marchi@efficios.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Gdb-prs
mailing list