On 16 November 2011 15:02, mrym <[email protected]> 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 OPTFLAGS=$(OPTFLAGS) /MDd /DDEBUG /D_DEBUG 2) Rebuild your program linking against GDAL 3) Check if you have symbols database generated (gdal18.pdb file size >20-30MB) 4) Check if GDAL links against Debug C/C++ Run-Tim dumpbin /ALL python32_d.dll | find /i "msvcr" 5) Execute your program under debugger, try to step in GDALAllRegister() 6) Check if you step into your own program at all > and i don't know what to do..:( I'd start with writing clear posts, describing in details steps what you do: IOW, http://catb.org/~esr/faqs/smart-questions.html#beprecise Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
