From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 4/4] gdb/mi: extend -file-list-exec-source-files command
Date: Mon, 26 Apr 2021 20:39:47 +0300 [thread overview]
Message-ID: <83v989hrmk.fsf@gnu.org> (raw)
In-Reply-To: <bd432df6bbeee80737a07a7bfee3bb0cc0b6a985.1619456691.git.andrew.burgess@embecosm.com> (message from Andrew Burgess on Mon, 26 Apr 2021 18:07:03 +0100)
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Mon, 26 Apr 2021 18:07:03 +0100
>
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -31,6 +31,17 @@
> equivalent of the CLI's "break -qualified" and "dprintf
> -qualified".
>
> + ** '-file-list-exec-source-files' can now accept a regular
> + expression for filtering, and accepts the flags --dirname,
> + --basename and --group-by-binary, making this command equivalent
> + of the cli 'info sources' command.
> +
> + In the non '--group-by-binary' mode an extra field
> + 'debug-fully-read' has been added to each source file tuple to
> + indicate if the debug information for the compilation unit
> + containing this source file has been fully read or not, the
> + values for this field are 'true' or 'false'.
This part is OK.
> +With no arguments this command returns a list of source files. Each
> +source file is represented by a tuple with the fields; @var{file},
> +@var{fullname}, and @var{debug-fully-read}. The @var{file} is the
> +display name for the file, while @var{fullname} is the absolute path
> +to the file. ^^^^^^^^^^^^^
^^^^^^^^^^^
GNU Coding Standards frown on calling "path" anything that is not a
PATH-style directory list. Please use "absolute name of the file"
instead.
> The @var{fullname} field can be elided if the absolute
> +path to the source file can't be computed.
Likewise.
> +If @code{--dirname} is provided then @var{regexp} is matched only
> +against the directory name of each source file. If @code{--basename}
> +is provided then @var{regexp} is matched against the source files
> +basename.
^^^^^^^^
"basenames", in plural.
> +If @code{--group-by-binary} is used then the format of the results is
> +changed. The results will now be a list of tuples, with each tuple
> +representing an object file (executable or shared libraries) loaded
> +into @value{GDBN}. The fields of these tuples are; @var{filename},
> +@var{debug-fully-read}, and @var{sources}. The @var{filename} is the
> +absolute path to the object file, @var{debug-fully-read} is a string,
^^^^^^^^^^^^^
"path" again
Thanks.
next prev parent reply other threads:[~2021-04-26 17:40 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 17:06 [PATCH 0/4] New option for 'info sources', also better MI support Andrew Burgess
2021-04-26 17:07 ` [PATCH 1/4] gdb: add new function quick_symbol_functions::has_unexpanded_symbols Andrew Burgess
2021-05-13 14:38 ` Simon Marchi
2021-05-13 17:29 ` Tom Tromey
2021-05-13 14:46 ` Simon Marchi
2021-04-26 17:07 ` [PATCH 2/4] gdb: make struct output_source_filename_data more C++ like Andrew Burgess
2021-05-13 14:58 ` Simon Marchi
2021-04-26 17:07 ` [PATCH 3/4] gdb: add new -group-by-binary flag to info sources command Andrew Burgess
2021-04-26 17:34 ` Eli Zaretskii
2021-05-13 15:05 ` Simon Marchi
2021-05-15 8:45 ` Andrew Burgess
2021-05-15 13:19 ` Simon Marchi
2021-04-26 17:07 ` [PATCH 4/4] gdb/mi: extend -file-list-exec-source-files command Andrew Burgess
2021-04-26 17:39 ` Eli Zaretskii [this message]
2021-05-13 15:47 ` Simon Marchi
2021-05-13 10:34 ` [PATCH 0/4] New option for 'info sources', also better MI support Andrew Burgess
2021-05-19 11:12 ` [PATCHv2 0/5] "info sources" - group by objfile Andrew Burgess
2021-05-19 11:12 ` [PATCHv2 1/5] gdb: add new function quick_symbol_functions::has_unexpanded_symbols Andrew Burgess
2021-05-19 11:12 ` [PATCHv2 2/5] gdb: make struct output_source_filename_data more C++ like Andrew Burgess
2021-05-19 11:12 ` [PATCHv2 3/5] gdb/mi: add regexp filtering to -file-list-exec-source-files Andrew Burgess
2021-05-19 11:51 ` Eli Zaretskii
2021-05-19 11:12 ` [PATCHv2 4/5] gdb/mi: add new --group-by-objfile flag for -file-list-exec-source-files Andrew Burgess
2021-05-19 11:44 ` Eli Zaretskii
2021-05-19 11:12 ` [PATCHv2 5/5] gdb: change info sources to group results by objfile Andrew Burgess
2021-05-19 11:53 ` Eli Zaretskii
2021-06-03 13:08 ` Simon Marchi
2021-06-03 9:27 ` [PATCHv2 0/5] "info sources" - group " Andrew Burgess
2021-06-03 13:15 ` Simon Marchi
2021-06-07 18:32 ` [PATCHv3 " Andrew Burgess
2021-06-07 18:32 ` [PATCHv3 1/5] gdb: add new function quick_symbol_functions::has_unexpanded_symbols Andrew Burgess
2021-06-07 18:32 ` [PATCHv3 2/5] gdb: make struct output_source_filename_data more C++ like Andrew Burgess
2021-07-05 12:31 ` Tom de Vries
2021-07-26 13:21 ` Andrew Burgess
2021-06-07 18:32 ` [PATCHv3 3/5] gdb/mi: add regexp filtering to -file-list-exec-source-files Andrew Burgess
2021-06-07 18:32 ` [PATCHv3 4/5] gdb/mi: add new --group-by-objfile flag for -file-list-exec-source-files Andrew Burgess
2021-06-07 18:32 ` [PATCHv3 5/5] gdb: change info sources to group results by objfile Andrew Burgess
2021-06-21 12:02 ` PING! Re: [PATCHv3 0/5] "info sources" - group " Andrew Burgess
2021-06-25 20:08 ` Andrew Burgess
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=83v989hrmk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.com \
--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).