From: Pedro Alves <pedro@palves.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: [PATCH] Explicitly mention yet-unloaded shared libraries in location spec examples
Date: Tue, 31 May 2022 12:13:54 +0100 [thread overview]
Message-ID: <329dd3bc-4a76-873c-006e-4e07aadc8d3c@palves.net> (raw)
In-Reply-To: <837d63j8tx.fsf@gnu.org>
On 2022-05-30 17:15, Eli Zaretskii wrote:
>>>> +Here are examples of typical situations that result in a location spec
>>>> +matching multiple concrete code locations in your program:
>>> Should we also enumerate some situations where a location spec cannot
>>> be completely resolved? The text talks about that possibility, but
>>> only in passing, with no details or practical examples.
>> I've added these examples under the multi-location examples:
>>
>> +And here are examples of typical situations that result in a location
>> +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.
>> +
>> +@item
>> +The location spec specifies a source file name, and there are no
>> +source files in the program with that name.
>> +
>> +@item
>> +The location spec specifies both a source file name and a source line
>> +number, and even though there are source files in the program that
>> +match the file name, none of those files has the specified line
>> +number.
>> +@end itemize
> Shouldn't this mention explicitly the frequent situation where the
> location specifies something in a yet-unloaded shared library?
>
Maybe. How about this.
From 4fc52ddcdf871c365a3abc6f681fb79ac473728a Mon Sep 17 00:00:00 2001
From: Pedro Alves <pedro@palves.net>
Date: Tue, 31 May 2022 12:06:50 +0100
Subject: [PATCH] Explicitly mention yet-unloaded shared libraries in location
spec examples
Change-Id: I05639ddb3bf620c7297b57ed286adc3aa926b7b6
---
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 b497901473d..7886f3eb3dd 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -9150,11 +9150,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
base-commit: 5541bfdc97936581c0ead915e9117e22f21bdb12
prerequisite-patch-id: 02daf94a0a458024d52b3a10e80608fd3e26738a
--
2.36.0
next prev parent reply other threads:[~2022-05-31 11:13 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 19:42 [PATCH v4] gdb/manual: Introduce location specs Pedro Alves
2022-05-27 14:16 ` Eli Zaretskii
2022-05-27 15:04 ` Pedro Alves
2022-05-27 15:52 ` Eli Zaretskii
2022-05-27 17:11 ` Pedro Alves
2022-05-27 17:31 ` Eli Zaretskii
2022-05-27 17:51 ` Pedro Alves
2022-05-27 18:23 ` Eli Zaretskii
2022-05-27 18:42 ` Pedro Alves
2022-05-27 18:50 ` Pedro Alves
2022-05-27 19:00 ` Eli Zaretskii
2022-05-27 19:30 ` Pedro Alves
2022-05-28 7:43 ` Eli Zaretskii
2022-05-30 14:38 ` Pedro Alves
2022-05-27 18:55 ` Eli Zaretskii
2022-05-27 19:05 ` Pedro Alves
2022-05-27 19:14 ` Eli Zaretskii
2022-05-27 19:17 ` Pedro Alves
2022-05-27 19:34 ` Eli Zaretskii
2022-05-27 19:38 ` Pedro Alves
2022-05-28 7:39 ` Eli Zaretskii
2022-05-30 14:44 ` [pushed v5] " Pedro Alves
2022-05-30 16:15 ` Eli Zaretskii
2022-05-31 11:05 ` [PATCH] Improve clear command's documentation Pedro Alves
2022-05-31 12:36 ` Eli Zaretskii
2022-05-31 13:04 ` Pedro Alves
2022-05-31 13:42 ` Eli Zaretskii
2022-05-31 14:47 ` Pedro Alves
2022-05-31 16:06 ` Eli Zaretskii
2022-05-31 11:13 ` Pedro Alves [this message]
2022-05-31 11:47 ` [PATCH] Explicitly mention yet-unloaded shared libraries in location spec examples Eli Zaretskii
2022-05-31 11:17 ` [pushed v5] gdb/manual: Introduce location specs Pedro Alves
2022-05-31 11:31 ` [PATCH] Improve break-range's documentation Pedro Alves
2022-05-31 11:55 ` Eli Zaretskii
2022-05-31 12:03 ` Pedro Alves
2022-05-31 12:09 ` Eli Zaretskii
2022-06-01 17:17 ` RTe: Location Specs (Was: [pushed v5] gdb/manual: Introduce location specs) Eli Zaretskii
2022-06-02 11:10 ` Pedro Alves
2022-06-02 11:49 ` Eli Zaretskii
2022-06-02 12:40 ` Pedro Alves
2022-06-02 12:56 ` Eli Zaretskii
2022-06-02 13:44 ` Pedro Alves
2022-06-02 16:37 ` Eli Zaretskii
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=329dd3bc-4a76-873c-006e-4e07aadc8d3c@palves.net \
--to=pedro@palves.net \
--cc=eliz@gnu.org \
--cc=gdb-patches@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).