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

[Hartmut]

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

I have also done a (completly fresh) mxe-octave build of the Octave "default"
version (built under Ubuntu 14.04). The Octave sources were used up to cset
ecce63c99c3f. This includes jwe's patch to "avoid mulitple definitions of
static function-scope vars".

My results under Windows 7 are:

* "test imread; clear all; test imread" gives NO crash
* "test imread; exit" gives NO segfault

(I have only tested the GUI versions.)

Everything seems perfect to me! Thanks for this patch, John.

@Avinoam  (and Philip): Could you double check in your mxe-octave file
"pkg/octave-4.1.0+.tar.gz" that you have really used the source files
INCLUDING jwe's patch? I wasn't able to download a patched tgz file until
today in the morning. An easy check is to look at line 208 in
"doc/interpreter/splineimage.m" if the semicolon after the demo code has been
added (from cset ecc63c99c3f).

    _______________________________________________________

Reply to this item at:

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

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