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: Fri, 29 Mar 2024 15:34:54 +0000 [thread overview] Message-ID: <bug-31573-4717-T5jqftAy7v@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 #6 from Tom de Vries <vries at gcc dot gnu.org> --- Hmm, actually, that seems to be right. Looking in the object, we have both ctf and dwarf info, with dwarf info: ... $ readelf -wi outputs/gdb.base/ctf-ptype/ctf-ptype0.o Contents of the .debug_info section: Compilation Unit @ offset 0: Length: 0x36 (32-bit) Version: 4 Abbrev Offset: 0 Pointer Size: 8 <0><b>: Abbrev Number: 1 (DW_TAG_compile_unit) <c> DW_AT_stmt_list : 0 <10> DW_AT_low_pc : 0 <18> DW_AT_high_pc : 563 <1a> DW_AT_name : (indirect string, offset: 0): /tmp/ccGk1NDi.s <1e> DW_AT_comp_dir : (indirect string, offset: 0x10): /data/vries/gdb/leap-15-4/build/gdb/testsuite <22> DW_AT_producer : (indirect string, offset: 0x3e): GNU AS 2.41.0 <26> DW_AT_language : 32769 (MIPS assembler) <1><28>: Abbrev Number: 2 (DW_TAG_subprogram) <29> DW_AT_name : (indirect string, offset: 0x4c): main <2d> DW_AT_external : 1 <2d> DW_AT_type : <0x38> <2e> DW_AT_low_pc : 0 <36> DW_AT_high_pc : 563 <1><38>: Abbrev Number: 3 (DW_TAG_unspecified_type) <1><39>: Abbrev Number: 0 ... So, why is gas generating dwarf info for main when we're using -gctf? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-29 15:34 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 [this message] 2024-03-30 8:41 ` vries at gcc dot gnu.org 2024-03-30 12:16 ` 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-31573-4717-T5jqftAy7v@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).