Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH, doc RFA] Add "skip regexp"
Date: Tue, 02 Feb 2016 16:10:00 -0000	[thread overview]
Message-ID: <83mvrjytyx.fsf@gnu.org> (raw)
In-Reply-To: <94eb2c0b86103073b2052abf11e5@google.com> (message from Doug	Evans on Tue, 02 Feb 2016 01:03:19 +0000)

> Date: Tue, 02 Feb 2016 01:03:19 +0000
> From: Doug Evans <dje@google.com>
> 
> With this patch one can specify the skip as:
> 
> skip regexp ^std::(allocator|basic_string)<.*>::~?\1 *\(

Thanks.

> 2016-02-01  Doug Evans  <dje@google.com>
> 
> 	New command "skip regexp regular-expression".
> 	* NEWS: Document the new feature.
> 	* skip.c (skip_kind): New enum.
> 	(skiplist_entry) <filename,function_name>: Delete.
> 	<kind,text,regex,regex_valid>: New members.
> 	(skiplist_entry_kind_name): New function.
> 	(make_skip_file, make_skip_function, make_skip_regexp): New function.
> 	(free_skiplist_entry, free_skiplist_entry_cleanup): New functions.
> 	(make_free_skiplist_entry_cleanup): New function.
> 	(skip_file_command): Update.
> 	(skip_function): Update.
> 	(compile_skip_regexp, skip_regexp_command): New functions.
> 	(skip_info): Update.
> 	(sal_and_fullname): New struct.
> 	(skip_file_p, skip_function_p, skip_regexp_p): New functions.
> 	(function_name_is_marked_for_skip): Update and simplify.
> 	(_initialize_step_skip): Add "skip regexp" command.
> 
> 	doc/
> 	* gdb.texinfo (Skipping Over Functions and Files): Document
> 	"skip regexp".

The documentation parts are approved, with the following nit:

> +Functions may be skipped by providing either a function name, linespec
> +(@pxref{Specify Location}), file name, or regular expression of the
> +function's name.                          ^^^^^^^^^^^^^^^^^^^^^^^^^
   ^^^^^^^^^^^^^^^
"regular expression that matches the function's name" is more accurate
(and you also use it elsewhere in the patch).

Otherwise, fine with me, thanks.


  reply	other threads:[~2016-02-02 16:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02  1:03 Doug Evans
2016-02-02 16:10 ` Eli Zaretskii [this message]
2016-02-04 13:47 ` Pedro Alves
2016-02-02 18:05 Doug Evans
2016-02-17  1:07 Doug Evans
2016-02-17 16:07 ` Eli Zaretskii
2016-02-29 18:55 ` Simon Marchi
2016-02-23 21:36 Doug Evans
2016-02-24  9:54 ` Joel Brobecker
2016-02-24 18:21   ` Doug Evans
2016-03-02 23:20 Doug Evans
2016-03-03 19:21 Doug Evans
2016-03-03 20:40 ` Simon Marchi
2016-03-15 19:45 Doug Evans

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=83mvrjytyx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dje@google.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