The Carbide.C++ debugger seems to promise "scripting" so that
I can define some sort of automatic actions to be taken when
breakpoints are hit.
And I see that certain trivial things are there:
- Skip one or more source statements
- Play a .WAV file
- Write something to the log
- Auto-resume after a fixed time delay
But I'd like to do something more along the lines of:
Can THAT be done?
Is that capability perhaps hiding in this fifth possibility
for a breakpoint action:
Am I missing the forest for the trees?
And, of course, is any of this stuff actually documented
anywhere (and if so, where)?