Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Hui Zhu <hui_zhu@mentor.com>
Cc: gdb-patches@sourceware.org, marc.khouzam@ericsson.com
Subject: Re: [PATCH] add -s option to make -break-insert support dprintf
Date: Thu, 28 Mar 2013 18:37:00 -0000	[thread overview]
Message-ID: <83y5d7wpvq.fsf@gnu.org> (raw)
In-Reply-To: <515451EA.1000200@mentor.com>

> Date: Thu, 28 Mar 2013 22:21:30 +0800
> From: Hui Zhu <hui_zhu@mentor.com>
> CC: Marc Khouzam <marc.khouzam@ericsson.com>, Eli Zaretskii <eliz@gnu.org>
> 
> This is the patches to add -s flags to make -break-info support dprintf.
> mi-dprintf.txt is for the code.
> mi-dprintf-doc.txt is for the doc.
> mi-dprintf-test.txt is for the test.
> 
> After this patch, you can use -s option to add dprintf.  To see mi-dprintf-doc.txt to get info about how to use this function.

Thanks.

> This is for NEWS:
>    ** The -s of MI command -break-insert can set a dynamic printf.

 "The new option -s of the MI command -break-insert sets a dynamic
  printf breakpoint."

> 2013-03-28  Hui Zhu  <hui@codesourcery.com>
> 
> 	* gdb.texinfo (GDB/MI Breakpoint Commands): Add "-s".
                                                    ^^^^^^^^
"Describe the -s option."

> --- a/doc/gdb.texinfo
> +++ b/doc/gdb.texinfo
> @@ -28784,7 +28784,9 @@ N.A.
>  @smallexample
>   -break-insert [ -t ] [ -h ] [ -f ] [ -d ] [ -a ]
>      [ -c @var{condition} ] [ -i @var{ignore-count} ]
> -    [ -p @var{thread-id} ] [ @var{location} ]
> +    [ -p @var{thread-id} ]
> +    [ -s "@var{template},@var{expression}[,@var{expression}@dots{}]" ]
> +    [ @var{location} ]
>  @end smallexample
>  
>  @noindent
> @@ -28824,6 +28826,29 @@ Make the breakpoint conditional on @var{
>  Initialize the @var{ignore-count}.
>  @item -p @var{thread-id}
>  Restrict the breakpoint to the specified @var{thread-id}.
> +@item -s "@var{location},@var{template},@var{expression}[,@var{expression}@dots{}]"

The format of the -s argument in @item is different from the format in
the @smallexample above.  Which one is correct?

> +Set a @ref{Dynamic Printf}.

Please don't use @ref as if it were an HTML "<a href" attribute; it is
not.  This produces ugly Info output.  Please use this style instead:

  Set a dynamic printf breakpoint (@pxref{Dynamic Printf}).

or this:

  Set a dynamic printf breakpoint, described in @ref{Dynamic Printf}.


  reply	other threads:[~2013-03-28 14:38 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28 17:44 Hui Zhu
2013-03-28 18:37 ` Eli Zaretskii [this message]
2013-03-29 16:12   ` Hui Zhu
2013-03-29 16:13     ` Eli Zaretskii
2013-04-09 23:31     ` Pedro Alves
2013-04-10 19:44       ` Marc Khouzam
2013-04-10 19:45         ` Pedro Alves
2013-04-11  6:15       ` Hui Zhu
2013-04-11 17:47         ` Pedro Alves
2013-04-12 14:56           ` Hui Zhu
2013-04-12 15:22             ` Pedro Alves
2013-04-15 18:59               ` Hui Zhu
2013-04-15 19:41                 ` Pedro Alves
2013-04-16  9:31                   ` Hui Zhu
2013-04-22  1:25                 ` Yao Qi
2013-04-12 16:03             ` Eli Zaretskii
2013-04-13 14:16         ` Tom Tromey
2013-04-15 18:04           ` Hui Zhu
2013-04-15 19:36             ` Pedro Alves
2013-04-16  9:31               ` Hui Zhu
2013-04-22  0:18                 ` Tom Tromey
2013-04-22  9:07                   ` Hui Zhu
2013-04-25  6:51                     ` Tom Tromey
2013-05-03  5:43                       ` Hui Zhu
2013-05-07 20:50                         ` Tom Tromey
2013-05-10 10:57                           ` Hui Zhu
2013-05-10 15:24                             ` Tom Tromey
2013-05-11  2:38                               ` Hui Zhu
2013-05-11  7:29                                 ` Eli Zaretskii
2013-05-13  3:39                                   ` Hui Zhu
2013-05-13 15:55                                     ` Eli Zaretskii
2013-05-14  4:56                                       ` Hui Zhu
2013-05-20  7:31                                         ` Hui Zhu
2013-05-20 15:44                                           ` Eli Zaretskii
2013-05-21  4:25                                             ` Hui Zhu
2013-05-21  8:10                                               ` [patch] Fix racy FAILs due to "read1" [Re: [PATCH] add -s option to make -break-insert support dprintf] Jan Kratochvil
2013-05-21  9:30                                                 ` Hui Zhu
2013-05-21 15:01                                                   ` [commit] " Jan Kratochvil
2013-05-22  1:05                                                     ` Hui Zhu
2013-05-23 14:03                                               ` [patch] Fix racy FAILs #2 " Jan Kratochvil
2013-05-24 15:37                                                 ` [commit] " Jan Kratochvil
2013-05-27 11:02                                                   ` Hui Zhu
2013-05-13 16:23                                 ` [PATCH] add -s option to make -break-insert support dprintf Tom Tromey

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=83y5d7wpvq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hui_zhu@mentor.com \
    --cc=marc.khouzam@ericsson.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