From: Pedro Alves <palves@redhat.com>
To: "Gustavo, Luis" <luis_gustavo@mentor.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [rfc target-side break conditions 1/5 v2] Documentation bits
Date: Thu, 23 Feb 2012 17:46:00 -0000 [thread overview]
Message-ID: <4F467963.4040701@redhat.com> (raw)
In-Reply-To: <4F450AA9.3020501@mentor.com>
On 02/22/2012 03:32 PM, Luis Gustavo wrote:
> +* New options
> +
> +set breakpoint condition-evaluation
> +show breakpoint condition-evaluation
> + Controls whether breakpoint conditions are evaluated by GDB ("gdb") or by
> + GDBserver ("target").
> + This option can improve debugger efficiency depending on the speed of the
> + target.
> +
> +* New remote packets
> +
> + The z0/z1 breakpoint insertion packets have been extended to carry
> + a list of conditional expressions over to GDBserver depending on the
suggest s/GDBserver/the remote stub/
(making clear the packet isn't only useful with GDB's own server.)
> +If a breakpoint is conditional, there are two evaluation modes: ``gdb'' and
> +``target''. If mode is ``gdb'', breakpoint condition evaluation is done by
> +@value{GDBN} on the host's side. If it is ``target'', then the condition
> +is evaluated by the target. The @code{info break} command shows
> +the condition on the line following the affected breakpoint, together with
> +its condition evaluation mode in between parentheses.
I'm probably confused by now, but I thought that the modes are now "host" and
"target". Other than that, no comment. I think the docs changes look great.
--
Pedro Alves
next prev parent reply other threads:[~2012-02-23 17:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 20:33 Luis Gustavo
2012-01-28 9:07 ` Eli Zaretskii
2012-02-22 16:19 ` Luis Gustavo
2012-02-23 17:46 ` Pedro Alves [this message]
2012-02-23 17:55 ` Luis Gustavo
2012-02-23 18:24 ` Pedro Alves
2012-02-24 12:38 ` Luis Gustavo
2012-02-07 21:42 ` Stan Shebs
2012-02-08 23:07 ` Luis Gustavo
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=4F467963.4040701@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=luis_gustavo@mentor.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