Howto debug c++ (SWIG) extension under Windows
Miki Tebeka
miki.tebeka at zoran.com
Wed Apr 27 07:16:08 EDT 2005
Hello Alexander,
> >>I can't figure out howto debug my c++ extension. If i compile it as
> >>release version, I've of course no chance to set a breakpoint.
> >This is not true. You *can* set breakpoints in release mode, make sure to
> >add debug information to your release build so you'll be able to see the
> >sources.
> >There are several cases (such as inlined functions) that you *can't* set
> >breakpoint to.
>
> Don't work because of my MSVCR71D.dll problem. It seems, that if I
> include DEBUG informations in my project, there is a reference to that
> (debug) DLL.
But I'm talking about *release* build.
> >>If I > compile as debug I get the Error-window:
> >>
> >>... missing MSVCR71D.dll ...
> >Just copy it (and msvcp71d.dll) from your c:\windows\system32 (or wherever
> >your windows is installed) to the "Debug" library (or to the Python install
> >library).
>
> I don't have the dll MSVCR71D.dll on my system path. What I'm a bit
> confused about is, that I can't even start python_d (installed by
> ActiveState DEBUG extension to ActivePython). It requires also the DLL.
>
> Does anybody know, where to get that DLL ?
Try "download MSVCR71D.dll" in google.
Another option if to compile you extension in debug mode but to link it to
the "regular" Python. Just undef _DEBUG when compiling the SWIG output
file.
Bye.
--
------------------------------------------------------------------------
Miki Tebeka <miki.tebeka at zoran.com>
http://tebeka.bizhat.com
The only difference between children and adults is the price of the toys
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 193 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-list/attachments/20050427/966de583/attachment.sig>
More information about the Python-list
mailing list