public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCHv2 3/5] gdb/mi: add regexp filtering to -file-list-exec-source-files
Date: Wed, 19 May 2021 14:51:43 +0300	[thread overview]
Message-ID: <83a6orq6uo.fsf@gnu.org> (raw)
In-Reply-To: <db581172ccc47e181f9d5d86fc6b2d6a79431c4a.1621421987.git.andrew.burgess@embecosm.com> (message from Andrew Burgess on Wed, 19 May 2021 12:12:40 +0100)

> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Wed, 19 May 2021 12:12:40 +0100
> 
> This commit extends the existing MI command
> -file-list-exec-source-files to provide the same regular expression
> based filtering that the equivalent CLI command "info sources"
> provides.
> 
> The new command syntax is:
> 
>   -file-list-exec-source-files [--basename | --dirname] [--] [REGEXP]

Thanks.

> + ** '-file-list-exec-source-files [--basename | --dirname] [--] [REGEXP]'
> +
> +    The existing -file-list-exec-source-files command now takes an
> +    optional REGEXP which is used to filter the source files that are
> +    included in the results.  By default REGEXP is matched against the
> +    full filename of the source file.
> +
> +    When one of --basename or --dirname is given then REGEXP is only
> +    matched against the specified part of the full source filename.

It is better to make the last sentence of the first paragraph to be
the first sentence of the second paragraph, since these describe the
same aspect of using REGEXP.

> +This commands returns information about the source files @value{GDBN}
> +knows about, it will output both the filename and fullname (absolute
> +file name) of a source file, though the fullname can be elided if this
> +information is not known.
               ^^^^^^^^^^^^
I'd suggest to say "is not known to @value{GDBN}", to make the issue
more clear.

> +name of the source file can't be computed. The field
                                            ^^
Two spaces between sentences, please (here and elsewhere).

> +@var{debug-fully-read} will be a string, either @code{true} or
> +@code{false}.  When @code{true} this indicates the full debug
                                  ^
Comma is missing there.

> +information for the compilation unit describing this file has been
> +read in.  When @code{false} the full debug information has not yet
                              ^
And there.

> +@value{GDBN} interpreting @var{regexp} as a command option (e.g. if
> +@var{regexp} starts with @samp{-}).

Please add either a comma or "@:" (without quotes) after "e.g.", so
that TeX won't interpret that as ending a sentence.

> +If @code{--dirname} is provided then @var{regexp} is matched only
                                  ^
Comma missing.

> +against the directory name of each source file.  If @code{--basename}
> +is provided then @var{regexp} is matched against the basename of each
              ^
And here.

  reply	other threads:[~2021-05-19 11:51 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
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 [this message]
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=83a6orq6uo.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).