public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "wqferr at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/32261] [RFE] Script that turns .S debug information into dwarf::assembler style Date: Mon, 11 Nov 2024 20:43:38 +0000 [thread overview] Message-ID: <bug-32261-4717-nOkLQmmTc8@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-32261-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=32261 --- Comment #10 from William Ferreira <wqferr at gmail dot com> --- I come here looking for help; I am confused with regards to some features of the Dwarf assembler. In line 503 of gdb.dwarf2/dwarf.exp, it states: If VALUE starts with the ":" character, then it is a label reference. The rest of VALUE is taken to be the name of a label, and DW_FORM_ref4 is used. See 'new_label' and 'define_label'. But in line 55 of gdb.dwarf2/dynarr-ptr.exp, I find: {DW_AT_type :$integer_label} Where both the : prefix for a label value and the TCL variable expansion symbol $ are used. From my understanding of the documentation pasted above, the correct usage would have been: {DW_AT_type :integer_label} Since integer_label is a label declared previously in the file. Could someone explain to me what I am missing, please? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-11-11 20:43 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-10-10 15:50 [Bug testsuite/32261] New: " guinevere at redhat dot com 2024-10-10 15:51 ` [Bug testsuite/32261] " guinevere at redhat dot com 2024-10-10 16:00 ` simon.marchi at polymtl dot ca 2024-10-10 16:03 ` guinevere at redhat dot com 2024-10-10 16:09 ` simon.marchi at polymtl dot ca 2024-10-10 17:31 ` tromey at sourceware dot org 2024-10-10 17:36 ` guinevere at redhat dot com 2024-10-10 20:29 ` wqferr at gmail dot com 2024-10-10 22:38 ` tromey at sourceware dot org 2024-10-10 22:46 ` wqferr at gmail dot com 2024-11-11 20:43 ` wqferr at gmail dot com [this message] 2024-11-25 16:59 ` wqferr at gmail dot com 2024-11-25 23:20 ` tromey at sourceware dot org 2024-11-27 17:47 ` wqferr at gmail dot com 2024-11-27 18:19 ` tromey at sourceware dot org 2024-11-27 18:40 ` wqferr at gmail dot com 2024-11-28 17:22 ` wqferr at gmail dot com 2024-11-29 18:20 ` tromey at sourceware dot org 2024-11-29 18:27 ` tromey at sourceware dot org 2024-11-29 21:01 ` wqferr at gmail dot com 2024-11-30 18:16 ` tromey at sourceware dot org 2024-11-30 19:36 ` wqferr at gmail dot com 2024-11-30 23:33 ` mark at klomp dot org 2024-12-02 20:06 ` guinevere at redhat dot com 2024-12-05 3:16 ` tromey at sourceware dot 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-32261-4717-nOkLQmmTc8@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).