Thanks Pawel.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=324843
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Pawel Piech
Sent: Tuesday, September 07, 2010 5:12 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] terminating a DFS debug session
Hi Dobrin,
It's a consequence of the following design decision:
The context elements that are shown in the Debug view (and other views) are
backed by an object that is returned from a service. When a debug session
is terminated, the debug services are terminated and the objects that they
managed are no longer accessible. To compensate for this, the UI
integration (view model) creates a dummy element to represent the terminated
process. However, since this dummy element is not backed by the data
object from the service and it's equals() method does not match the original
element, the view does not re-select this dummy element.
I think it's fair to call this a bug with a [cdi] "feature parity"
bug. It may require some creativity but it can be fixed :-)
Cheers,
Pawel
On 09/07/2010 11:50 AM, Alexiev, Dobrin wrote:
I noticed that when I terminate a DSF GDB debug session the
selection of the debug view disappears.
Also, I have an action that is calling IAdaptable
debugContext = DebugUITools.getDebugContext();
When I terminate the debug session the return debugContext is
now referring to an object that is not in the debug view and probably is not
valid:
debugContext.toString() returns
gdb[6].proc[].threadGroup[],gdb[6].proc[].OSthread[1]).thread[1].frame[0]
Is this intentional? If not, should I file a bug for this?
I tested the Java debugger. When I terminate a Java debug
session the selection of the debug view doesn’t disappear.
Thanks
Dobrin
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev