From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH, doc RFA] Add "skip regexp"
Date: Wed, 17 Feb 2016 16:07:00 -0000 [thread overview]
Message-ID: <83y4ajuxq1.fsf@gnu.org> (raw)
In-Reply-To: <001a113452243e6481052bece0b3@google.com> (message from Doug Evans on Wed, 17 Feb 2016 01:07:38 +0000)
> Date: Wed, 17 Feb 2016 01:07:38 +0000
> From: Doug Evans <dje@google.com>
> Cc: gdb-patches@sourceware.org
>
> Eli: Heads up, rewritten docs, needing re-approval.
Thanks for the heads-up.
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -127,6 +127,14 @@ show max-value-size
> allocate for value contents. Prevents incorrect programs from
> causing GDB to allocate overly large buffers. Default is 64k.
>
> +skip -file file
> +skip -gfile file-glob-pattern
> +skip -function function
> +skip -rfunction regular-expression
> + A generalized form of the skip command, with new support for
> + glob-style file names and regular expressions for function names.
> + Additionally, a file spec and a function spec may now be combined.
> +
This part is OK.
> +@item -gfile @var{file-glob-pattern}
> +@itemx -gfi @var{file-glob-pattern}
> +Functions in files matching @var{file-glob-pattern} will be skipped
> +over when stepping.
> +
> +@smallexample
> +(gdb) skip -gfi utils/*.c
> +@end smallexample
Is there a way to protect wildcard characters? If so, I think we
should mention it.
> +For example, there is generally no need to step into C++ std::string
C@t{++}, and "std::string" should be in @code.
Also, this description should have a couple of @cindex entries, as
readers are likely to look for it without remembering that the
command's name is "skip".
The documentation is OK with those fixed.
Thanks.
next prev parent reply other threads:[~2016-02-17 16:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 1:07 Doug Evans
2016-02-17 16:07 ` Eli Zaretskii [this message]
2016-02-29 18:55 ` Simon Marchi
-- strict thread matches above, loose matches on Subject: below --
2016-03-15 19:45 Doug Evans
2016-03-03 19:21 Doug Evans
2016-03-03 20:40 ` Simon Marchi
2016-03-02 23:20 Doug Evans
2016-02-23 21:36 Doug Evans
2016-02-24 9:54 ` Joel Brobecker
2016-02-24 18:21 ` Doug Evans
2016-02-02 18:05 Doug Evans
2016-02-02 1:03 Doug Evans
2016-02-02 16:10 ` Eli Zaretskii
2016-02-04 13:47 ` Pedro Alves
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=83y4ajuxq1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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