public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/30026] New: ctf test program gives weird results with "list"
Date: Thu, 19 Jan 2023 18:53:15 +0000	[thread overview]
Message-ID: <bug-30026-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30026
           Summary: ctf test program gives weird results with "list"
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: tromey at sourceware dot org
  Target Milestone: ---

I tried the test programs in gdb.ctf.
If I debug one and then type "list" I get very weird output:

murgatroyd. ../gdb -nx ./outputs/gdb.ctf/cross-tu-cyclic/cross-tu-cyclic 
[...]
(gdb) list
1       ^?ELF^B^A^A


What's happening here is that in ctfread.c:scan_partial_symbols:

  if (strcmp (fname, ".ctf") == 0)
    {
      fname = bfd_get_filename (of->obfd.get ());
      isparent = true;
    }

  ctf_psymtab *pst = create_partial_symtab (fname, tup->arc, cfp,
                                            partial_symtabs, of);

IOW, ctfread is saying that the source file for this psymtab
is the executable itself, which is clearly wrong.

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

             reply	other threads:[~2023-01-19 18:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 18:53 tromey at sourceware dot org [this message]
2023-01-19 18:56 ` [Bug symtab/30026] " tromey at sourceware dot org
2023-01-23 11:45 ` nick.alcock at oracle dot com
2023-01-23 13:15 ` tromey at sourceware dot org
2023-01-26 14:05 ` nick.alcock at oracle dot com
2023-01-30  4:16 ` tromey at sourceware dot org
2023-12-06 11:58 ` nick.alcock at oracle dot com
2023-12-06 20:10 ` 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-30026-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).