Re: [PATCH 2/2] new tracepoint downloaded MI notification.

Pedro Alves
2012-11-22T18:33:00Z

Marc Khouzam wrote:

> In older GDB versions, when creating a tracepoint during a trace run,
> that tracepoint would not be pushed to the target until the next
> trace run. The idea is that a frontend could indicate which tracespoints
> were active on the target and which were not.
>
> Now that GDB pushes new tracepoints to the target immediately, that
> use-case may not apply, but I wonder if there are other situations
> where some tracepoints will be on the target and other will not?

What about the case of connecting to a target that is tracing, after
disconnected tracing? Do we already tell the frontend somehow which
tracepoints are active on the target? Should tracepoints have an
"installed on target" field?

Yao Qi wrote:
> On 11/01/2012 03:09 AM, Marc Khouzam wrote:
>> Now that GDB pushes new tracepoints to the target immediately, that
>> use-case may not apply, but I wonder if there are other situations
>> where some tracepoints will be on the target and other will not?
>
> Yes, the pending tracepoints won't be downloaded after tracing is started until they are resolved. The notification is required for this case.

Ok. If the answer to my question above is yes, it might be this
notification ends up unnecessary in favor of a generic
=breakpoint-modified.

--
Pedro Alves