public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "blarsen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/31267] New: Bad hint when listing before reading symbols
Date: Fri, 19 Jan 2024 10:29:19 +0000	[thread overview]
Message-ID: <bug-31267-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31267
           Summary: Bad hint when listing before reading symbols
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: cli
          Assignee: unassigned at sourceware dot org
          Reporter: blarsen at redhat dot com
  Target Milestone: ---

If a user tries to list source lines before GDB reads the inferior's symbols,
they get the following error message:

    (gdb) list
    No symbol table is loaded.  Use the "file" command.

However, the error persists when the command is used, like so:

    (gdb) file ~/a.out                                  
    Reading symbols from ~/a.out...                     
    (No debugging symbols found in ~/a.out)             
    (gdb) list                                          
    No symbol table is loaded.  Use the "file" command. 

GDB should instead realize if the command has been used and instead tell the
user that symbols haven't been read yet (and suggest a command, eitehr 'start'
or some command to read the symbols)

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

             reply	other threads:[~2024-01-19 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 10:29 blarsen at redhat dot com [this message]
2024-01-19 15:45 ` [Bug cli/31267] " tromey at sourceware dot org
2024-01-20  8:36 ` sam at gentoo 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-31267-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).