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 testsuite/31573] [gdb/testsuite] FAIL: gdb.base/ctf-ptype.exp: ptype linked list structure Date: Sat, 30 Mar 2024 12:16:41 +0000 [thread overview] Message-ID: <bug-31573-4717-bBh28qklfn@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31573-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31573 --- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> --- First let's note that: - gcc defaults to dwarf5 starting gcc 11 (with some exceptions, which do not include linux) - gcc supports -gctf starting gcc 12. The compiler I'm using is a bit different, because: - it's gcc 12 so it supports gtcf, but - it also defaults to dwarf4 instead of dwarf5. I investigated on another system, where the gcc both supports gctf and defaults to dwarf5, found that no dwarf info is generated in that case, and investigated why. It's because in the dwarf4 default case, there's only: ... .file "ctf-ptype.c" ... which does not active this code in dwarf2_directive_filename: ... /* A .file directive implies compiler generated debug information is being supplied. Turn off gas generated debug info. */ if (debug_type == DEBUG_DWARF2) purge_generated_debug (false); debug_type = DEBUG_NONE; ... while with the dwarf5 default case, there's also: ... .file 0 "/home/vries/gdb" "/data/vries/gdb/src/gdb/testsuite/gdb.base/ctf-ptype.c" ... which does active that bit of code, setting debug_type to DEBUG_NONE, which means no dwarf is generated. So, another way of dealing with this would be to set debug_type to DEBUG_NONE also for the simple .file directive. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2024-03-30 12:16 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-29 7:00 [Bug testsuite/31573] New: " vries at gcc dot gnu.org 2024-03-29 7:24 ` [Bug testsuite/31573] " vries at gcc dot gnu.org 2024-03-29 8:21 ` vries at gcc dot gnu.org 2024-03-29 8:31 ` vries at gcc dot gnu.org 2024-03-29 9:00 ` vries at gcc dot gnu.org 2024-03-29 11:52 ` vries at gcc dot gnu.org 2024-03-29 15:34 ` vries at gcc dot gnu.org 2024-03-30 8:41 ` vries at gcc dot gnu.org 2024-03-30 12:16 ` vries at gcc dot gnu.org [this message]
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-31573-4717-bBh28qklfn@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: linkBe 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).