[Octave-bug-tracker] [bug #44420] Memory leaks in 4.0 RC

[Rik]

Follow-up Comment #3, bug #44420 (project octave):

I ran into that same problem of running valgrind on the dispatch program
octave rather than on octave-cli or octave-gui.  I worked around it by editing
my copy of run-octave.


  elif [ "x$1" = "x-valgrind" ]; then
    ##driver="valgrind --tool=memcheck"
    driver="valgrind -v --tool=memcheck --leak-check=yes
--leak-resolution=high --num-callers=50 --log-file=valgrind.log"
    octave_executable="$builddir/src/octave-cli"
    shift




    _______________________________________________________

Reply to this item at:

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

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