[Gdal-dev] Tracing into GDAL
rogerjames99 at btinternet.com
Thu Aug 14 13:50:51 EDT 2003
You also need to make sure that you have the matching *.pdb file
accessible preferably in the same directory as the .dll.
> -----Original Message-----
> From: gdal-dev-admin at remotesensing.org [mailto:gdal-dev-
> admin at remotesensing.org] On Behalf Of Ben Discoe
> Sent: 14 August 2003 16:52
> To: gdal-dev at remotesensing.org
> Subject: RE: RE : [Gdal-dev] Tracing into GDAL
> gdal_i.lib definitely! The static gdal library is huge, especially
> debug version. gdal_i.lib/gdal11.dll, and the debug versions
> gdal_id.lib/gdal11d.dll are quite compact, relatively speaking. On my
> machine, it's 20MB vs. 2MB/3MB.
> > -----Original Message-----
> > From: gdal-dev-admin at remotesensing.org
> > [mailto:gdal-dev-admin at remotesensing.org] On Behalf Of mathieu_gdal
> > Sent: Thursday, August 14, 2003 10:13 AM
> > To: gdal-dev at remotesensing.org
> > Subject: RE : [Gdal-dev] Tracing into GDAL
> > Thank you for the answer, but...
> > it does not work on my computer!
> > Do you use gdal_i.lib or gdal.lib?
> > Mathieu
> > -----Message d'origine-----
> > De : gdal-dev-admin at remotesensing.org
> > [mailto:gdal-dev-admin at remotesensing.org] De la part de Ben Discoe
> > Envoyé : mercredi 13 août 2003 16:46
> > À : gdal-dev at remotesensing.org
> > Objet : RE: [Gdal-dev] Tracing into GDAL
> > Mathieu,
> > You don't need to "put gdal11.pdb in my app's application". Leave
> > files such as .pdb in their original locations (generally
> > with the .lib)
> > so that they will be found. You should be able to trace into GDAL
> > functions with MSVC; i do it all the time.
> > -Ben
> Gdal-dev mailing list
> Gdal-dev at remotesensing.org
More information about the Gdal-dev