This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Add autoload-breakpoints [3/7] ReportAsync-doc
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Hui Zhu <hui_zhu at mentor dot com>
- Cc: gdb-patches at sourceware dot org, stan_shebs at mentor dot com
- Date: Tue, 20 Mar 2012 19:30:20 +0200
- Subject: Re: [PATCH] Add autoload-breakpoints [3/7] ReportAsync-doc
- References: <4F6450D2.9030109@mentor.com> <83y5qz359r.fsf@gnu.org> <4F688533.1050705@mentor.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Tue, 20 Mar 2012 21:25:07 +0800
> From: Hui Zhu <hui_zhu@mentor.com>
> CC: <gdb-patches@sourceware.org>, <stan_shebs@mentor.com>
>
> >> +The @value{GDBN} remote serial protocol includes @dfn{reportasync},
> >> +packets that the stub can report status or do an operation in any time.
> >
> > I don't understand the "do an operation in any time" part. What does
> > it mean in practice?
>
> It is means that after gdb connected with the stub, the stub can report
> when the inferior is running and GDB is waiting it, or inferior is
> stoped and GDB just control it.
> It make the stub can report the status for any time.
You mean, as in "asynchronously"?
> > And I don't understand what you mean by "needs to be handled as a
> > simple packet". If that's a reference to something discussed earlier
> > in the manual, please add here a cross-reference to that part.
>
> That means when the stub send a shake hands package ^ and wait the
> reply, if it got a package that is not ^. Then the shake hands is fail.
> It need give up this shake hands and begin to handle this packet that
> it just get.
> For example:
> Stub send a ^ to GDB. It readchar, and got a $. It should not drop
> this $, After that, it will got "c#csum". It need handle the package
> "$c#csum".
I still don't understand why you used the word "simple". "Simple" as
opposed to what other packet handling?
> > After the handshake, the stub can send @samp{reportasync} packets to
> > @value{GDBN}, using the same packet format as in simple remote serial
> > protocol.
> >
> > Is this only for the failed handshake? If so, perhaps we need to tell
> > what happens when the handshake succeeds.
>
> No, this is for success.
The problem here is that you again used "simple protocol", and before
that you mentioned "simple packet" when the handshake failed.
So this again boils down to the same question: why do you use the word
"simple" in this context?