RFC: new struct breakpoint component cond_language...

[Joel Brobecker]

> Tracepoints add an extra wrinkle to this concept - when connecting
> to a target that is currently running a trace, tracepoint conditions
> can be uploaded from the target, and in their original source form,
> and so have to be reparsed.  So to make this work in the
> multi-language case, it seems like the tracepoint download should
> include the language somehow.

I am not very familiar with tracepoints, but I think I see what
is happening (disconnecting GDB from the target?). It seems to me
that, indeed, tracepoints need to download and upload the condition
language as well. In particular:

> But then I wonder - when uploading a tracepoint, we receive both the
> computed address and the source form of that address, so in theory
> we can always deduce the correct language by working back from the
> tracepoint address.

I do not think so; At the time when the user declares the tracepoint
condition, I am assuming that we check the language mode, and that if
it is not auto, then we use the current_language as the condition
language, regardless of the language of the source. As a result,
the condition language cannot be determined from the tracepoint address.

-- 
Joel