That's cool :) Is there any particular performance penalty to compiling *with* OGRAPISPY_ENABLED and then running *without* OGR_API_SPY_FILE/OGR_API_SPY_SNAPSHOT_PATH set?
Rob :) On Sun, Aug 31, 2014 at 11:34 PM, Even Rouault <[email protected]> wrote: > Hi, > > This will not be of interest for the crowds, but mainly for OGR driver > developers (and potentially also to get precise bug reports from users). > I'm > currently adding update capabilities to the MITAB driver, and while playing > with QGIS, there are sometimes sequences of OGR calls that trigger bugs, > but > that I had issues to replicate afterwards. This spy mechanism enables to > have > recording of all relevant calls to be able to replicate them exactly > afterwards. > > Doc to use it : http://www.gdal.org/ograpispy_8h.html > > Related autotest script : > http://svn.osgeo.org/gdal/trunk/autotest/ogr/ograpispy.py > > Even > > -- > Spatialys - Geospatial professional services > http://www.spatialys.com > _______________________________________________ > gdal-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/gdal-dev > -- *Koordinates*PO Box 1604, Shortland St, Auckland 1140, New Zealand Phone +64-9-966 0433 koordinates.com <https://koordinates.com/about>
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
