In Plato, executing a program with the debugger. When I say 'clear all breakpoints', I would expect these to be cleared in the configuration file, x.ini. However, when clearing all break points and setting new ones, upon resuming the execution, the system still stops at old break points. When I go into the configuration file, x.ini, the list of all previous breakpoints is still there. I have to remove them from the x.in files and start over. Why is this? Sid Kraft
Breakpoints
It sounds like there is something that needs fixing. I will make a note to investigate.
Hi Paul: Any luck on finding out why this is happening? Sid Kraft
No. It is on the list of things to do as time permits.
In Plato, select Options from the Tools menu. Under Environment and General, select 'Integrate with SDBG'.
With this setting you should find that the break points are passed back correctly to Plato. Otherwise SDBG runs independently and Plato can pass break points to SDBG via the command line but there is no mechanism for passing information back again.
Curious why this integration with sdbg is not a default? Do Plato use its own debugger? (I do not know Plato, still walking circles around it. May be some day...)
It's not obvious which would be preferred. The 'integrated' version may have some advantages but does not have all of the functionality.
Plato does not have its own debugger. Either way it runs SDBG as a separate application.
For 64 bit applications it would be nice if we were able to provide a fully integrated debugger. This would mean taking code from SDBG64 and putting it into a DLL that could be accessed directly from Plato.