How to build custom debug engines for VS2005?
We built a custom debug engine, using the TextInterpreter sample as a guide,
five years ago, and have managed to build high-value debuggers since then.
I have everything working porting our plug-ins from VS200[23] to '05,
except the debuggers don't work. And now I see in the Beta 2 Readme
item 15:
"The TextInterpreter sample is not working."
I feel we're being left high and dry here. What kind of resolution can
we expect for those of us building custom debug engines that don't involve
managed code generation?
- Eric
the bug will be fixed for RTM, the intention is to have this functionality working in the final SDK.
this is not the only issue with the beta2 SDK as evidenced in the readme and there is no intention to slight custom debug engines. it is beta, after all.
there is a suggestion in the readme ( 5 ) for creating a custom debug engine, and given you already have one working that may allow you to make progress.
hth
Building is not my problem (anymore -- this wchar_t problem seemed to have
everyone baffled at the Jan '05 devlab in Redmond. It was certainly a blocker
for me).
The problem is that my built engine doesn't launch, and I don't know why, and I
can't use the SDK as a reference to check mine against, as it doesn't work either.
Yes, I'm frustrated. We're finding lots of interest in people getting beta level
plugins for VS 8, and we can't deliver.
How binary-compatible
is VS 8? I'm going to try plugging in an engine built with
the VS 7.1 API, and see what happens later today. Right now I'm dealing with
C# changes...
Thanks,
Eric
I'd appreciate some elaboration on this point, since we don't have an existing debug engine (yet). We solved the wchar_t issue referred to in readme(5), but obviously are unable to launch the TextInterpreter sample due to the "not working" issue.
When you say "the bug will be fixed for RTM" - does that mean
(a) there a bug in VS2005 Beta 2 that prevents launching custom debug engines, or
(b) there is a bug in the TextInterpreter sample but with proper implementation one can launch a custom debug engine, or
(c) something else?
thanks
donb
