Hi, On Tue, 20 Feb 2024 at 21:44, Robert Coup <robert.c...@koordinates.com> wrote:
> Hi Simon, > > On Tue, 20 Feb 2024 at 21:11, Simon Eves <simon.e...@heavy.ai> wrote: > >> Here's the stack trace for the original assert. Something is stepping on >> scratch_ to make it 0x1000000000 instead of null, which it starts out as >> when the flatbuffer object is created, but by the time it gets to >> allocating memory, it's broken. >> > > What happens if you set a watchpoint in gdb when the flatbuffer is created? > > watch -l myfb->scratch > or watch *0x1234c0ffee > Or I've also had success with Mozilla's rr: https://rr-project.org/ — you can run to a point where scratch is wrong, set a watchpoint on it, and then run the program backwards to find out what touched it. Rob :)
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
