Re: [cdt-dev] Remote debugging and live execution

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

Hi Stephen,

It sounds sensible to me to ease the flow of having some information
that is showing for the "most applicable" context when no relevant
debug context is actually active.

It would be worth considering how it may interact and/or reuse
implementation details of "pinned" contexts for views?

Have you started working on such a patch? Are you looking for guidance
on how to add such functionality?

Jonah

~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com


On 24 June 2016 at 17:24, Flynn, Stephen <Stephen.Flynn@xxxxxxx> wrote:
> From my post to the CDT forum:
>
> Hello all,
> I have been developing a plugin for Eclipse CDT for my company for the past several years. One of the things that has given me headaches is that most debug views are not active unless the current context is a suspended/ stopped thread or a trace frame. All the while, commands sent via the console are easily handled by the gdbserver/stub.
>
> This may have made sense years ago, and still makes sense for particular views (Registers View comes to mind). But for the majority of views that rely on information retrieved from the remote target this information is available whether or not the context is in a suspended state.
>
> My questions: Is the current paradigm employed by Eclipse for debugging remote targets too restrictive in allowing views to be populated by information readily available from the remote target? Is this something worth submitting a bug report for?
>
> Stephen Flynn
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cdt-dev