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

[John W. Eaton]

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

I'm just doing "make check >& make-check-log".

This runs (in the build directory):


cd test && $(SHELL) ../run-octave $(RUN_OCTAVE_OPTIONS) --norc --silent
--no-history $(abs_top_srcdir)/test/fntests.m $(abs_top_srcdir)/test


In my case, RUN_OCTAVE_OPTIONS is empty.

fntests.m just sets up some options and eventually calls __run_test_suite__,
but with some directory arguments.  So I'm not sure what is significantly
different.  Looking at the log, about 20k of that is from fontconfig.  About
half of that is tagged as "Direct leak" and the other half "Indirect".

I'll try your method and see what I get.  You could try the "make check" test
instead and see if it is different for you.

    _______________________________________________________

Reply to this item at:

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

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