Hi,
I'm working on a project that is implementing a custom debug engine in Visual Studio. So far the DE/VS package/EE are built, installed and running correctly except for a few peculiar issues. They all relate to one thing (I think) but here's the most reproducible example I've found (obviously I don't expect you to be able to do this as you don't have our package):
1) Start debugging
2) Set breakpoint
3) Breakpoint is correctly hit and code is paused
4) Locals, call stack and threads window all correctly filled out (within what we would expect our code to be capable of)
5) Watch window: All existing watch statements correctly filled out.
6) Add new watch expression : Correctly filled out but:
VS then seems to lose all context. It forgets the call stack, current line of code in the document and local variables.
7) Refresh or add another watch expression : VS says "Unable to evaluate expression"
VS does still know the code is broken. Clicking step over/into/out or continue then causes VS to refresh on next line and then we're back to step 3 again...
It's very bizarre. I have tried huge amounts of debugging our DE/VS package/EE etc. but it seems that after the first watch expression is evaluated, VS gives up. It never calls the DE or EE again! It doesn't try to get the stack frame or document context again (so far as I can tell) and the second watch expression never gets passed to the EE or anything!
Are we missing an interface/function implementation? Or are we missing an event callback or some flag somewhere? What can cause VS to think code is broken, but not know where it is any more?!
Thanks very much,
Ed