R: [Gdal-dev] trivial (?) optimization for gdal.i:GDALReadRaster( )

Frank Warmerdam warmerdam at pobox.com
Thu Feb 5 16:43:12 EST 2004


Andrey Kiselev wrote:
> On Thu, Feb 05, 2004 at 05:18:00PM +0100, Vincent Schut wrote:
> 
>>I'm sorry but I don't know how to invoke gdb to debug a python script,
>>so I don't have much more information.
> 
> 
> It is easy.
> 
> $ gdb python
> 
> and then 'run /path/to/script.py' in the debugger's command prompt.
> 
> 						Andrey

Right,

The only thing I would add is that it can be hard to set breakpoints
in GDAL since the shared library isn't loaded when python is in it's
main().  Sometimes I introduce a wait call at some strategic point in
GDAL (ie. GDALAllRegister()) to give me a chance to control-c gdb after
gdal has been loaded ... then I can set a breakpoint.

Best regards,

-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent




More information about the Gdal-dev mailing list