Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-debug-dev] automatic switch of instruction stepping mode

Dobrin,

There is an enhancment request for this feature -
https://bugs.eclipse.org/bugs/show_bug.cgi?id=79872. But I would prefer to
move this feature to the Eclipse Debug Framework and make the global step
actions retargettable, similar to the "Run To Line" action, for example. I
submitted an enhancement request to the Eclipse platform
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=80323). If they decide to
implement it in 3.1 we will use it for our implementation, otherwise we can
aplly your patch.

Thanks,
Mikhail
----- Original Message ----- 
From: "Alexiev, Dobrin" <dalexiev@xxxxxx>
To: <cdt-debug-dev@xxxxxxxxxxx>; <cdt-ui-dev@xxxxxxxxxxx>
Sent: Wednesday, December 15, 2004 5:47 PM
Subject: [cdt-debug-dev] automatic switch of instruction stepping mode


As part of our beta product we implemented a feature that automatically
switches between instruction level debugging and source level debugging
based on which view or editor is currently active.

I think many embedded IDEs have similar behavior since it is pretty
common to debug machine instructions. Many of the customers don't have
the source code so it makes sense for them to often switch between
assembly and C debugging, but the current CDT requires the user to
manually trigger the instruction stepping mode on and off.

We enhanced CDT to automatically switch between instruction and source
stepping mode biased on the active view or editor or keyboard focus. If
the user clicks or activates the disassembly view the stepping mode
automatically becomes instruction stepping. If the user clicks or
activates a source editor it will turn off instruction stepping and go
to source stepping.

In case some users are not happy with the automatic behavior we have a
toolbar and a menu that turns on/off the automatic switch.

Another feature we added is automatically opening of the disassembly
window if the target is halted and there is no source line associated
with the current PC. Correctly me if I am wrong, but I think that in
that case CDT only updates the disassembly window but doesn't try to
open or activate it.

If people think that these features are valuable for the general user or
if we need a way to augment this feature I am ready to submit the
changes I did.

Dobrin Alexiev
Texas Instruments
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-debug-dev





Back to the top