public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Pedro Alves <palves@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Explicitly mention yet-unloaded shared libraries in location spec examples
Date: Tue, 31 May 2022 11:50:43 +0000 (GMT)	[thread overview]
Message-ID: <20220531115043.A1CBD383665F@sourceware.org> (raw)

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

commit d7f735269f78cce3ae9b8dd1a96013d185f0c883
Author: Pedro Alves <pedro@palves.net>
Date:   Tue May 31 12:06:50 2022 +0100

    Explicitly mention yet-unloaded shared libraries in location spec examples
    
    Change-Id: I05639ddb3bf620c7297b57ed286adc3aa926b7b6

Diff:
---
 gdb/doc/gdb.texinfo | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 3cf4e2c73c0..8c85c5a0c82 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -9124,11 +9124,13 @@ spec matching no code locations in your program at all:
 @itemize @bullet
 @item
 The location spec specifies a function name, and there are no
-functions in the program with that name.
+functions in the program with that name, or they only exist in a
+yet-unloaded shared library.
 
 @item
 The location spec specifies a source file name, and there are no
-source files in the program with that name.
+source files in the program with that name, or they only exist in a
+yet-unloaded shared library.
 
 @item
 The location spec specifies both a source file name and a source line


                 reply	other threads:[~2022-05-31 11:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220531115043.A1CBD383665F@sourceware.org \
    --to=palves@sourceware.org \
    --cc=gdb-cvs@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).