[Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave

[Mike Miller]

Follow-up Comment #44, bug #47372 (project octave):

I don't think I'm getting the same results that you are. I have built the
default branch with


--disable-java --without-opengl --without-qt --enable-address-sanitizer-flags
--enable-bounds-check CFLAGS="-O0 -ggdb3" CXXFLAGS="-O0 -ggdb3" FFLAGS="-O0
-ggdb3"


and I get no segfault when I do


./run-octave
octave:1> test imread
PASSES 5 out of 5 tests
octave:2> quit


Is there something else you are doing to provoke the segfault you are seeing
from the GraphicsMagick-linked code? Any ASAN_OPTIONS or LSAN_OPTIONS in your
environment?

When I run this in gdb I do indeed see threads starting up when "test imread"
runs, but exiting shows no segfault. And as I reported earlier, I'm able to
run a full "make check" with no segfaults, either during or on exit. Running
again now to confirm that it still completes for me.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47372>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/