public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30742] [gdb/help] help "maint print symbols"/"help maint print psymbols" mentions minimal symbols
Date: Mon, 14 Aug 2023 16:27:11 +0000	[thread overview]
Message-ID: <bug-30742-4717-t73eMCeqbk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30742-4717@http.sourceware.org/bugzilla/>

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

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=980111642db44891500f53c12a939487d95deb68

commit 980111642db44891500f53c12a939487d95deb68
Author: Tom de Vries <tdevries@suse.de>
Date:   Mon Aug 14 18:27:02 2023 +0200

    [gdb] Fix maint print symbols/psymbols help text

    Consider the help text of "maint print symbols":
    ...
    (gdb) help maint print symbols
    Print dump of current symbol definitions.
    Usage: mt print symbols [-pc ADDRESS] [--] [OUTFILE]
           mt print symbols [-objfile OBJFILE] [-source SOURCE] [--] [OUTFILE]
    Entries in the full symbol table are dumped to file OUTFILE,
    or the terminal if OUTFILE is unspecified.
    If ADDRESS is provided, dump only the file for that address.
    If SOURCE is provided, dump only that file's symbols.
    If OBJFILE is provided, dump only that file's minimal symbols.
    ...
    and "maint print psymbols":
    ...
    (gdb) help maint print psymbols
    Print dump of current partial symbol definitions.
    Usage: mt print psymbols [-objfile OBJFILE] [-pc ADDRESS] [--] [OUTFILE]
           mt print psymbols [-objfile OBJFILE] [-source SOURCE] [--] [OUTFILE]
    Entries in the partial symbol table are dumped to file OUTFILE,
    or the terminal if OUTFILE is unspecified.
    If ADDRESS is provided, dump only the file for that address.
    If SOURCE is provided, dump only that file's symbols.
    If OBJFILE is provided, dump only that file's minimal symbols.
    ...

    The OBJFILE lines mistakingly mention minimal symbols.

    Fix this by reformulating as "dump only that object file's symbols".

    Also make the ADDRESS lines more clear by using the formulation: "dump only
    the symbols for the file with code at that address".

    Tested on x86_64-linux.

    Co-Authored-By: Eli Zaretskii <eliz@gnu.org>

    PR gdb/30742
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30742

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

  reply	other threads:[~2023-08-14 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 12:57 [Bug gdb/30742] New: " vries at gcc dot gnu.org
2023-08-14 16:27 ` cvs-commit at gcc dot gnu.org [this message]
2023-08-14 16:27 ` [Bug gdb/30742] " vries at gcc dot gnu.org
2023-08-15  3:28 ` 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-30742-4717-t73eMCeqbk@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).