I’ve ran into a wall while working on the sample implementation of a debug
engine using ATL COM. Is there a workaround? Is this a known issue or did I
perhaps do something incorrect?
The intent of this was to follow the sample closely per Microsoft’s
documentation at
ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.VSSDK.v80/dv_vsdbgsdk/html/9097b71e-1fe7-48f7-bc00-009e25940c24.htm
While following the tutorial, I ran into a few bumps and mitigated as
follows:
1.) The dbgmetric[d].lib libraries were originally compiled with
/Zc:wchar_t-, but as of VC++ 8, the default is to define it. To workaround
this and use the libraries, use Project Properties->Languages->Treat wchar_t
as Native type => No
2.) The include files and external libraries are located in different
folders than specified in the tutorial. The path should look like ". . .
.//Visual Studio 2005
SDK/2006.04/VisualStudioIntegration/Archive/DebuggerSDK/Includes" and ". . .
. //Visual Studio 2005 SDK/2006.04/VisualStudioIntegration/Common/Lib"
In the final step of the sample implementation the compilation of MyCPrj
fails because _vsnwprintf was declared deprecated from VS 7.1 to VS 8.0. This
is yet another piece of the SDK that appears to not have been updated. The
suggestion from the output window is to use _vsnprintf_s instead, however the
function is called in strsafe.h which is not a part of the MyCPrj, rather it
is a part of Microsoft's general "Safer String Handling in C" released in
2002. Since the goal of this project isn't to create a more robust safe
string class in C, rather to create a custom debug engine I'll just turn off
"treat warnings as errors" in the compiler. After doing this, the MyCPrj
compilation succeeded.
3.) At the very end of the sample implementation walk through is an
explanation of how to configure the sample MyC project to target the Text
Interpreter debug engine previously created. The documentation for this is
located at
ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.VSSDK.v80/dv_vsdbgsdk/html/5aca8b48-f760-4475-a89a-e1cc6c66a4da.htm
After following the instructions step by step, I reach step 18. Once I
select “Properties” I get an assertion when using the debug build of the MyC
project and an application (Visual Studio) crash when using the release build.
Other than the aforementioned workarounds, I did not deviate from the
instructions given in the sample.
"Gary Chang[MSFT]" - 21 Jun 2006 08:49 GMT
Hi,
Thank you posting!
>After following the instructions step by step, I reach step 18.
>Once I select “Properties�I get an assertion
>when using the debug build of the MyC project
>and an application (Visual Studio) crash when
>using the release build.
In order to research this issue, would you please provide more detailed
information about it, what's assertion failure you get with the debug
version?
Thanks!
Best regards,
Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Thread-Topic: How do I implement a custom debug engine per the sample
without cr
>thread-index: AcaUoMNPZRXbLZ1JQ4WB8BLXbjF74A==
>X-WBNR-Posting-Host: 134.134.136.5
[quoted text clipped - 19 lines]
>
>I’ve ran into a wall while working on the sample implementation of a
debug
>engine using ATL COM. Is there a workaround? Is this a known issue or did I
>perhaps do something incorrect?
>
>The intent of this was to follow the sample closely per Microsoft’s
>documentation at :
ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.VSSDK.v80/dv_vsdbgsdk/html/9097b71e-1
fe7-48f7-bc00-009e25940c24.htm
> While following the tutorial, I ran into a few bumps and mitigated as
>follows:
[quoted text clipped - 24 lines]
>Interpreter debug engine previously created. The documentation for this is
>located at:
ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.VSSDK.v80/dv_vsdbgsdk/html/5aca8b48-f
760-4475-a89a-e1cc6c66a4da.htm
>After following the instructions step by step, I reach step 18. Once I
>select “Properties�I get an assertion when using the debug build of
the MyC
>project and an application (Visual Studio) crash when using the release build.
>
>Other than the aforementioned workarounds, I did not deviate from the
>instructions given in the sample.
"Gary Chang[MSFT]" - 23 Jun 2006 06:22 GMT
Hi,
How are the things going?
I have preformed some tests in my local machine with VSSDK 2006 April, I
don't get the compiling issue on my side. But I could repro the assertion
failure problem while perform that walkthrough. It seems casued by a null
string.
Currently I will performing some further research on this issue and will
get back to you as soon as possible. I appreciate your patience.
Thanks!
Best regards,
Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
"Gary Chang[MSFT]" - 27 Jun 2006 06:54 GMT
Hi,
I have perform some tests with this issue, I found the problem is in the
MyCPkgs sample, even the unmodified MyCPkgs sample would also cause such an
assertion failure while you attemp to open its project properties' page.
It appears the upgraded MyCPkgs projects are not fully compatible with the
new VC2005's library.
Thanks!
Best regards,
Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Yan-Hong Huang[MSFT] - 29 Jun 2006 11:03 GMT
Hello,
I am reviewing the issue thread. How is everything going? If you are still
monitoring the issue thread and the problem is not resolved yet, could you
please post a update here? We will contineously work with you on it.
Thanks very much.
Sincerely,
Yanhong Huang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.