public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug ada/29335] [gdb/ada, debug-types] FAIL: gdb.ada/local-enum.exp: print v1 element
Date: Thu, 20 Apr 2023 08:57:20 +0000 [thread overview]
Message-ID: <bug-29335-4717-HadftGeAJ5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29335-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29335
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
With gnatmake-11:
...
$ readelf -WS leap-15-4/build/gdb/testsuite/outputs/gdb.ada/local-enum/local |
grep debug | sed 's/.*\.//' | awk '{print $1}'
debug_aranges
debug_info
debug_abbrev
debug_line
debug_str
debug_loc
debug_ranges
debug_types
...
With gnatmake-12:
...
$ readelf -WS leap-15-4/build/gdb/testsuite/outputs/gdb.ada/local-enum/local |
grep debug | sed 's/.*\.//' | awk '{print $1}'
debug_aranges
debug_info
debug_abbrev
debug_line
debug_str
debug_loc
debug_ranges
...
So, the test-case passes with gnatmake-12 because .debug_types is no longer
generated.
I wrote some C program that has an enum:
...
$ cat test.c
enum a {
b, c ,d
};
enum a
foo (enum a e)
{
return e;
}
int
main (void)
{
foo (b);
return 0;
}
...
and tried:
...
$ gcc-11 test.c -g -fdebug-types-section; readelf -S -W a.out | grep -c
debug_types
1
$ gcc-12 test.c -g -fdebug-types-section; readelf -S -W a.out | grep -c
debug_types
1
...
so it's not that support for fdebug-types-section disappeared.
It's just that the ada compiler no longer generates the .debug_types section
for a DW_TAG_type_unit which is used here:
...
<1><15f2>: Abbrev Number: 19 (DW_TAG_array_type)
<15f3> DW_AT_name : (indirect string, offset: 0x1e5a): local__a2
<15f7> DW_AT_GNAT_descriptive_type: signature: 0x76b135b6e23e0b79
<15ff> DW_AT_type : <0x15ce>
...
referenced using a DW_AT_GNAT_descriptive_type.
The FAIL is back if we add additional_flags=-fgnat-encodings=all.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-04-20 8:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 8:00 [Bug ada/29335] New: " vries at gcc dot gnu.org
2023-04-19 18:24 ` [Bug ada/29335] " tromey at sourceware dot org
2023-04-20 8:03 ` vries at gcc dot gnu.org
2023-04-20 8:57 ` vries at gcc dot gnu.org [this message]
2023-04-27 16:30 ` tromey at sourceware dot org
2023-09-07 10:27 ` vries at gcc dot gnu.org
2023-09-07 15:10 ` vries at gcc dot gnu.org
2023-09-07 19:53 ` cvs-commit at gcc dot gnu.org
2023-09-07 19:54 ` vries at gcc dot gnu.org
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=bug-29335-4717-HadftGeAJ5@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).