This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch 5/5] Document


On Thursday 17 November 2011 03:24:47, Yao Qi wrote:
> +until they are resolved.  The resolution of pending tracepoints requires
> +@value{GDBN} support--in the remote target, when @value{GDBN}

I think it really needs to be three dashes.

> +disconnects from the remote stub, pending tracepoints still exist but
> +can not be resolved while @value{GDBN} is disconnected.

Sorry to be picky, but I'm trying to read this from a user's perspective,
and it still confuses me.  What does "pending tracepoints still exist"
mean?  Do you mean they still exist in GDB?  That's true for all kinds
of breakpoints, so it doesn't add anything.  If you mean that they exist
on the target, then what does it mean for a pending tracepoint to exist
on the target?  What we're really trying to say is that pending tracepoints
don't work with disconnected tracing.  How about:

The resolution of pending tracepoints requires @value{GDBN} support---
when debugging with the remote target, and @value{GDBN} disconnects from the
remote stub (@pxref{disconnected tracing}), pending tracepoints can not be
resolved (and downloaded to the remote stub) while @value{GDBN} is
disconnected.

?

-- 
Pedro Alves


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]