Extension compile problems

Hi all,

I am tring to compile the windbg extension sample
extcpp. I have the latest ddk, debug tools and visual studio. I also
followed everything in the readme file and i
keep getting to following error:
error LNK2019: unresolved external symbol ___CxxFrameHandler3.
I also tried to write my own batch file to compile the sample and still have
the same error.

Any ideas how to solve this?

thanks,
uy

UY:

The problem is that EngCpp requires the VC8 (perhaps 2003; I can’t
recall which; you’ll have to dump the import library to find out, unless
you find out from someone else or now yourself) runtimes, and you are
linking against a DDK that doesn’t contain them - or something along
those lines. I believe that if you change SOURCES to directly reference
VC8/2003 (assuming that you have the required one installed; if it is
2003, one of the newer DDK’s will have it, I believe) CRTs, it will
link. At this point you might get the pleasure of trying to get this
extension to load, particularly if you are running on a machine that has
never had VC8/2003 installed. This is the point at which I decided that
the old DbgEng style would be just fine, as getting EngCpp to load
involved, in my case, at least, creating something called a “Setup
Project” in VC8.

Best of luck,

mm

>> xxxxx@gmail.com >>>
Hi all,

I am tring to compile the windbg extension sample
extcpp. I have the latest ddk, debug tools and visual studio. I also
followed everything in the readme file and i
keep getting to following error:
error LNK2019: unresolved external symbol ___CxxFrameHandler3.
I also tried to write my own batch file to compile the sample and still
have
the same error.

Any ideas how to solve this?

thanks,
uy


You are currently subscribed to windbg as: xxxxx@evitechnology.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

In the 6.6.07 release we have included the source code for engextcpp.cpp
so that you can build ExtCpp yourself. This allows full control over
all compile options.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Wednesday, October 11, 2006 2:41 AM
To: Kernel Debugging Interest List
Subject: Re: [windbg] Extension compile problems

UY:

The problem is that EngCpp requires the VC8 (perhaps 2003; I can’t
recall which; you’ll have to dump the import library to find out, unless
you find out from someone else or now yourself) runtimes, and you are
linking against a DDK that doesn’t contain them - or something along
those lines. I believe that if you change SOURCES to directly reference
VC8/2003 (assuming that you have the required one installed; if it is
2003, one of the newer DDK’s will have it, I believe) CRTs, it will
link. At this point you might get the pleasure of trying to get this
extension to load, particularly if you are running on a machine that has
never had VC8/2003 installed. This is the point at which I decided that
the old DbgEng style would be just fine, as getting EngCpp to load
involved, in my case, at least, creating something called a “Setup
Project” in VC8.

Best of luck,

mm

>> xxxxx@gmail.com >>>
Hi all,

I am tring to compile the windbg extension sample extcpp. I have the
latest ddk, debug tools and visual studio. I also followed everything in
the readme file and i keep getting to following error:
error LNK2019: unresolved external symbol ___CxxFrameHandler3.
I also tried to write my own batch file to compile the sample and still
have the same error.

Any ideas how to solve this?

thanks,
uy


You are currently subscribed to windbg as: xxxxx@evitechnology.com To
unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com