Hi,
(I repost here some of my wishes I already talked about elsewhere. Only to keep them at the right place...)
I really miss a runtime Hardware Stack watch window (as in MPLAB) in the software debugger ....
Hardware stack watch
Re: Hardware stack watch
What do you want that we show in that window?david68 wrote:I really miss a runtime Hardware Stack watch window (as in MPLAB) in the software debugger ....
Thanks for your quick reply !
Basically, the same thing as in MPLAB: level of stack being used, and return locations.
Of course, the return adress as itself may be of less importance with a high-level language such as yours (it could be replaced by the name of the sub being called), but at least the stack usage.
The call tree is a good tool, but it may not be enough, especially in controlled recurse calls, or complex multi-level interrupts.
I think it could be easy to implement in your debugger:
- You can detect at runtime each "CALL" instruction or interrupt of the application and add the name of the sub to the stack
- Detect all RETURN or RETFIE, and clear last level.
Any other idea is, of course, welcome.
Basically, the same thing as in MPLAB: level of stack being used, and return locations.
Of course, the return adress as itself may be of less importance with a high-level language such as yours (it could be replaced by the name of the sub being called), but at least the stack usage.
The call tree is a good tool, but it may not be enough, especially in controlled recurse calls, or complex multi-level interrupts.
I think it could be easy to implement in your debugger:
- You can detect at runtime each "CALL" instruction or interrupt of the application and add the name of the sub to the stack
- Detect all RETURN or RETFIE, and clear last level.
Any other idea is, of course, welcome.
