How to use -list-target-features MI command

Simon Marchi
Sun May 27 22:13:00 GMT 2018

On 2018-05-18 17:16, Jan Vrany wrote:
> Hmm, just thinking loud: I don't know the details of Pedro's work but
> I guess in case of multiple targets, it'd make sense to have two
> "target-connected" and "target-disconnected" events instead of one
> "target-changed" (as in my attempt). This would work for current
> codebase with only one target at time.
> As for -list-target-features - I presume each target would have some
> kind of identifier (just like threads or breakpoints do). Then one can
> just extend -list-target-features with --target <target id> option.
> If --target is not specified, it would return features of "currently
> selected target". This way it'd be backward compatible.

Yep, that makes sense.


More information about the Gdb mailing list