From: Eli Zaretskii <eliz@gnu.org>
To: Ross Morley <ross@tensilica.com>
Cc: gdb-patches@sourceware.org, maxim@tensilica.com
Subject: Re: [PATCH] Program Breakpoints
Date: Sat, 18 Apr 2009 06:21:00 -0000 [thread overview]
Message-ID: <8363h2jxcw.fsf@gnu.org> (raw)
In-Reply-To: <49E92DCB.4000007@tensilica.com>
> Date: Fri, 17 Apr 2009 18:32:59 -0700
> From: Ross Morley <ross@tensilica.com>
> CC: Maxim Grigoriev <maxim@tensilica.com>
>
> The user manual has been updated. I will update the internals
> manual after this patch has been (possibly changed and) accepted.
Thank you. I have a few comments for the documentation patch:
> +Some programs may contain embedded break or trap instructions that are
> +unknown to GDB. These are called @dfn{program breakpoints} because they
^^^
"@value{GDBN}".
> +belong to the program itself. If encountered, a target may stop execution
> +and report this to GDB along with how much to increment the PC to step
> +over it (a target is not required to do this).
Please don't talk about a "target" in the user's manual: this
terminology is unknown to them. Please talk about the "inferior" or
the "program being debugged".
> +@item program-breakpoint
> +A program breakpoint (trap instruction unknown to GDB) was reached.
^^^
"@value{GDBN}"
> @@ -26723,6 +26731,12 @@
> @value{GDBN} should use @samp{qXfer:libraries:read} to fetch a new
> list of loaded libraries. @var{r} is ignored.
>
> +@item trap
> +The packet indicates that a target-specific break or trap instruction
> +was hit. @var{r} is the size of the instruction if the PC is pointing
> +to it, else 0 (for example if the hardware already incremented the PC).
> +@var{r} is ignored if the instruction was planted by @value{GDBN}.
> +
> The packet indicates that the target cannot continue replaying
Something strange happened with this hunk. In the current CVS, the
manual in this part looks like this:
@cindex shared library events, remote reply
@item library
The packet indicates that the loaded libraries have changed.
@value{GDBN} should use @samp{qXfer:libraries:read} to fetch a new
list of loaded libraries. @var{r} is ignored.
@cindex replay log events, remote reply
@item replaylog
The packet indicates that the target cannot continue replaying
logged execution events, because it has reached the end (or the
beginning when executing backward) of the log. The value of @var{r}
will be either @samp{begin} or @samp{end}. @xref{Reverse Execution},
for more information.
So it seems to me that you are plugging your part in the middle of
another @item, but then where's the "@item replaylog" line and the one
preceding it, with @cindex"? What am I missing?
Finally, please make sure every period that ends a sentence has 2
spaces, not 1, after it.
> --- gdb/NEWS 31 Mar 2009 20:21:06 -0000 1.305
> +++ gdb/NEWS 17 Apr 2009 18:55:25 -0000
> @@ -3,6 +3,10 @@
>
> *** Changes since GDB 6.8
>
> +* GDB now supports handling (embedded) program break or trap instructions
> +that are unknown to GDB. These are called program breakpoints because they
> +belong to the program itself.
This is good, but I suggest to add a sentence telling how would GDB
manifest these program breakpoints. Also, "program breakpoints"
should be in quotes, as you are introducing a new term.
Thanks.
next prev parent reply other threads:[~2009-04-18 6:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 1:33 Ross Morley
2009-04-18 6:21 ` Eli Zaretskii [this message]
2009-04-18 6:30 ` Eli Zaretskii
2009-04-18 7:58 ` Ross Morley
2009-04-18 1:51 [Fwd: [PATCH] Program Breakpoints] Ross Morley
2009-04-22 1:22 ` [PATCH] Program Breakpoints Ross Morley
2009-04-22 3:12 ` Eli Zaretskii
2009-04-27 7:07 ` Ross Morley
2009-04-30 18:05 Ross Morley
2009-04-30 18:30 ` Pedro Alves
2009-04-30 19:14 ` Ross Morley
2009-05-04 22:49 ` Ross Morley
2009-05-04 23:14 ` Pedro Alves
2009-05-04 23:17 ` Ross Morley
2009-05-13 4:24 ` Ross Morley
2009-05-19 17:30 [Fwd: Re: [PATCH] Program Breakpoints] Ross Morley
2009-05-19 18:58 ` Pedro Alves
2009-05-27 1:49 ` [PATCH] Program Breakpoints Ross Morley
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=8363h2jxcw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=maxim@tensilica.com \
--cc=ross@tensilica.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