Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Justin Lebar <justin.lebar@gmail.com>
Cc: dje@google.com, stanshebs@earthlink.net, gdb-patches@sourceware.org
Subject: Re: Status of 'blacklist' patch?
Date: Thu, 20 Oct 2011 20:40:00 -0000	[thread overview]
Message-ID: <83ipnjs9i1.fsf@gnu.org> (raw)
In-Reply-To: <CAFWcpZ7UuD23wChztKuxPuYCM8FdUfEOqzcHT85YHusoCOvRZw@mail.gmail.com>

> From: Justin Lebar <justin.lebar@gmail.com>
> Date: Sun, 16 Oct 2011 12:40:39 -0400
> Cc: Stan Shebs <stanshebs@earthlink.net>, gdb-patches@sourceware.org
> 
> Added a NEWS entry in this patch.

Thanks.

> +* GDB now allows you to skip over uninteresting functions and files when
                           ^^^^^^^^^
I think either "step over" or just "skip".

> +@node Skipping Over Functions and Files
> +@subsection Skipping Over Functions and Files
> +@cindex skip

This @cindex entry would be better if it just said what the subsection
name says:

 @cindex skipping over functions and files

> +The program you are debugging may contain some functions which are
> +uninteresting to debug.  The @code{skip} comand lets you tell @value{GDBN} to
> +skip over a file or function when stepping.

Again, I think this is better:

  ... to skip a function or all functions in a file ...

> +A more flexible solution is to execute @code{skip boring}.  This instructs
                                          ^^^^^^^^^^^^^^^^^^
@kbd{skip boring}, since this is something the user types on the
keyboard.

> +You can also instruct @value{GDBN} to skip all functions in a file, with, for
> +example, @code{skip file boring.c}.

What happens if I have a function called "file" in the same program?
IOW, to what degree is "file" a reserved keyword here?

> +@table @code
> +@kindex skip
> +@kindex skip function

No need for two @kindex entries here, the second one is enough.

> +stepping.  (@pxref{Specify Location}) 

Just @xref, and no parentheses, like so:

  @xref{Specify Location}.

> +@item Type
> +@samp{function} or @samp{file}

The text below the @item line should be at least one complete
sentence.

> +being skipped.  If you've set a function skip on a function which has not yet
> +been loaded, this field will contain @samp{<PENDING>}.  Once a shared library
> +which has the function is loaded, @code{info break} will show the function's
                                           ^^^^^^^^^^
I guess you meant "info skip", right?

Okay with those changes.

Thanks.


  parent reply	other threads:[~2011-10-20 20:18 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 12:12 Diego Novillo
2011-10-06 14:08 ` Justin Lebar
2011-10-06 15:51   ` Stan Shebs
2011-10-06 20:16     ` Justin Lebar
2011-10-10 12:34       ` Stan Shebs
2011-10-11 21:34         ` Justin Lebar
2011-10-11 23:54           ` Doug Evans
2011-10-16 19:22             ` Justin Lebar
2011-10-20 19:46               ` Tom Tromey
2011-10-25 20:07                 ` Justin Lebar
2011-10-25 20:41                   ` Pedro Alves
2011-10-25 21:25                     ` Justin Lebar
2011-10-20 20:40               ` Eli Zaretskii [this message]
2011-10-25 16:47                 ` Justin Lebar
2011-10-25 16:53                   ` Eli Zaretskii
2011-10-25 19:52                     ` Justin Lebar
2011-10-25 20:13                       ` Eli Zaretskii
2011-10-25 20:30                         ` Justin Lebar
2011-10-26  1:06                           ` Stan Shebs
2011-10-26  3:45                             ` Justin Lebar
2011-10-26  5:37                               ` Stan Shebs
2011-10-26  8:10                                 ` Joel Brobecker
2011-10-26 13:28                             ` Eli Zaretskii
2011-10-26 15:11                               ` Justin Lebar
2011-10-28 18:18                                 ` Tom Tromey
2011-10-28 19:48                                   ` Justin Lebar
2011-10-28 19:53                                     ` Tom Tromey
2011-10-28 19:49                                 ` Tom Tromey
2011-10-28 19:55                                   ` Justin Lebar
2011-10-28 20:37                                     ` Tom Tromey
2011-10-31 15:52                                       ` Justin Lebar
     [not found]                                         ` <4EAF2E0E.7080508@earthlink.net>
2011-11-01 14:53                                           ` Justin Lebar
2011-11-02 22:43                                             ` Maciej W. Rozycki
2011-11-02 23:52                                               ` Stan Shebs
2011-11-03  0:20                                                 ` Maciej W. Rozycki
2011-11-03  3:54                                               ` Eli Zaretskii
2011-11-03 14:32                                                 ` Tom Tromey
2011-11-03 16:54                                                   ` Eli Zaretskii
2011-11-03 18:04                                                   ` Maciej W. Rozycki
2011-11-03 18:25                                                     ` Eli Zaretskii
2011-11-03 19:01                                                       ` Stan Shebs
2011-10-06 17:19   ` Diego Novillo
2011-10-06 17:33   ` Tom Tromey
2011-10-06 17:37     ` Diego Novillo

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=83ipnjs9i1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=justin.lebar@gmail.com \
    --cc=stanshebs@earthlink.net \
    /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