On 16 November 2011 15:52, mrym wrote:
> Thanks, i've done all of the things you wrote,but i'm still can't debug..
My palantír has broken, I can't help.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Member of ACCU, http://accu.org
_
Thanks, i've done all of the things you wrote,but i'm still can't debug..
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/can-not-debug-gdal1-8-1-at-visual-studio-2008-tp7000116p7000821.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.
_
2011/11/16 Mateusz Łoskot :
> 4) Check if GDAL links against Debug C/C++ Run-Tim
>
> dumpbin /ALL python32_d.dll | find /i "msvcr"
Obviously, I made mistake when copying this from my .bat script.
It should read:
dumpbin /ALL gdal18.dll | find /i "msvcr"
--
Mateusz Loskot, http://mateusz.loskot.
On 16 November 2011 15:02, mrym wrote:
> Ok. i see this message too "gdal18.dll, Binary was not built with debug
> information." i've replaced /MD with /MDd in flags for debug and build gdal
> again, but i still cannot debug gdal functions.
1) Not build but rebuild GDAL with correct flags
OPTFLA
Ok. i see this message too "gdal18.dll, Binary was not built with debug
information." i've replaced /MD with /MDd in flags for debug and build gdal
again, but i still cannot debug gdal functions. and i don't know what to
do..:(
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.c
