Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] multi debug context stepping in DSF

Thanks Pawel, this is what I am looking for. 
The fix works well with my selection policy which blocks the change of selection if currently there are two or more threads selected. 

Currently we don't display source. 
I guess our customers will use multiple registers/expressions views and use pinning to see data for each thread. 

One way would be to have different editor areas per core - left and right in case of two. Just a wish....not much thinking yet...

Thanks
Dobrin

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Pawel Piech
Sent: Thursday, July 21, 2011 5:04 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] multi debug context stepping in DSF

Hi Dobrin,
I think bug 345020 is what you're probably interested in.  Let us know 
how disabling the selection change works out.  One problem i don't see 
how to solve is which source do you display?

Cheers,
Pawel

On 07/20/2011 02:26 PM, Alexiev, Dobrin wrote:
> I am trying to implement multi context stepping.
>
> First, I overwrote DsfSuspendCommand, DsfResumeCommand and DsfStep*Command to enabled the commands if multiple execution context are selected.
>
> Next, When I multi select and execute Suspend/Step/Resume I don't want the selection to change, because the assumption is the user will continue with multi select operations. To achieve that I overwrote DefaultDsfSelectionPolicy to block the change of selection if currently multiple execution context are selected.
>
> Now the next problem - since there is no debug context change, my Suspend/Step/Resume commands don't update - they reflect the old state.
>
> Does anyone know what is the right way to update the Suspend/Step/Resume when at the same time the selection change is being blocked.
>
> Thanks
> Dobrin
>
>
>
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top