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 symtab/29160] New: [gdb, ctf+dwarf] FAIL: gdb.base/ctf-constvars.exp: print vox
Date: Fri, 20 May 2022 08:38:18 +0000	[thread overview]
Message-ID: <bug-29160-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29160

            Bug ID: 29160
           Summary: [gdb, ctf+dwarf] FAIL: gdb.base/ctf-constvars.exp:
                    print vox
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

On openSUSE Tumbleweed, with gcc 12.1.0, which supports -gctf, I run into:
...
FAIL: gdb.base/ctf-constvars.exp: print vox
...

AFAICT this is due to:
...
  /* Read the CTF section only if there is no DWARF info.  */
  if (!has_dwarf2 && ei.ctfsect)
    {
      elfctf_build_psymtabs (objfile);
    }
...
and the the exec has both ctf and dwarf:
...
$ readelf -S -W outputs/gdb.base/ctf-constvars/ctf-constvars
  ...
  [27] .ctf              PROGBITS        0000000000000000 0052cc 00054f 00     
0   0  1
  [28] .debug_aranges    PROGBITS        0000000000000000 003160 000120 00     
0   0 16
  [29] .debug_info       PROGBITS        0000000000000000 003280 000988 00     
0   0  1
  [30] .debug_abbrev     PROGBITS        0000000000000000 003c08 000282 00     
0   0  1
  [31] .debug_line       PROGBITS        0000000000000000 003e8a 00024f 00     
0   0  1
  [32] .debug_str        PROGBITS        0000000000000000 0040d9 0004bc 01  MS 
0   0  1
  [33] .debug_line_str   PROGBITS        0000000000000000 004595 000144 01  MS 
0   0  1
  [34] .debug_rnglists   PROGBITS        0000000000000000 0046d9 000042 00     
0   0  1
...

This due to the linked in startup files having dwarf info:
...
$ readelf --dwarf-depth=1 -wi outputs/gdb.base/ctf-constvars/ctf-constvars |
grep name
    <1a>   DW_AT_name        :   ../sysdeps/x86_64/start.S
    <3a>   DW_AT_name        :   ../sysdeps/x86/abi-note.c
    <510>   DW_AT_name        :  init.c
    <551>   DW_AT_name        :  static-reloc.c
    <957>   DW_AT_name        :  ../sysdeps/x86_64/crti.S
    <97a>   DW_AT_name        :  ../sysdeps/x86_64/crtn.S
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-05-20  8:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20  8:38 vries at gcc dot gnu.org [this message]
2022-06-02 14:24 ` [Bug symtab/29160] " jamborm at gcc dot gnu.org
2022-10-12 15:17 ` 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-29160-4717@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).