After loading a LAS file, if the resolution base is then changed and a new LAS file is loaded, the program segfaults. The following backtrace reports the problem to be in the PointBucket header.
#0 0x000000000045a2bb in PointBucket::getNumberOfPoints (this=0x7fff5e3dcac0, resolution=0)
at /users/rsg/besm/.build/include/lidar/quadtree/PointBucket.h:155
#1 0x000000000045f33e in TwoDeeOverview::drawpointsfrombuckets (this=0x7ffff5b90a80, buckets=0x7fffe03f0000, numbuckets=1214, drawnbucketsarray=
0x7ffff589d200, cachedonly=true) at src/TwoDeeOverview.cpp:509
#2 0x000000000045f109 in TwoDeeOverview::mainimage (this=0x7ffff5b90a80, buckets=0x7fffe03f0000, numbuckets=1214) at src/TwoDeeOverview.cpp:413
#3 0x00000000004c0981 in DrawWorker::run (this=0x7fffe1429800) at src/DrawWorker.cpp:121
#4 0x0000000000458a5c in sigc::bound_mem_functor0<void, Worker>::operator() (this=0x7ffff5a14958) at /usr/include/sigc++-2.0/sigc++/functors/mem_fun.h:1787
#5 0x00000000004583b0 in sigc::adaptor_functor<sigc::bound_mem_functor0<void, Worker> >::operator() (this=0x7ffff5a14950)
at /usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:251
#6 0x0000000000457997 in sigc::internal::slot_call0<sigc::bound_mem_functor0<void, Worker>, void>::call_it (rep=0x7ffff5a14920)
at /usr/include/sigc++-2.0/sigc++/functors/slot.h:103
#7 0x0000003230a428dd in ?? () from /lib64/libglibmm-2.4.so.1
#8 0x000000307b46a305 in ?? () from /lib64/libglib-2.0.so.0
#9 0x0000003079c07d14 in start_thread () from /lib64/libpthread.so.0
#10 0x00000030798f167d in clone () from /lib64/libc.so.6
After loading a LAS file, if the resolution base is then changed and a new LAS file is loaded, the program segfaults. The following backtrace reports the problem to be in the PointBucket header.