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

[John W. Eaton]

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

Rik: I'm doing as you suggest in comment #70.  I'll have a changeset soon.

I've been finding cases to work on by using nm on all object files and looking
for multiple instances of "guard variable for ..." that have the same variable
name.  As I understand it, these are the compiler generated global variables
that track whether a static variable is initialized.  So if there is only one
instance of a guard variable, then I think the static variable should only be
initialized once.

c++filt helps with name mangling.

I set KEEP_BUILD := 1 in the mxe-octave Makefile, then I used the following
commands in the tmp-stable-octave/octave-4.0.1/.build directory:


$ files=$(find . -name '*.o')
$ for f in $files ; do i686-w64-mingw32-nm $f | i686-w64-mingw32-c++filt |
grep 'guard variable' ; done | sort | uniq -c | sort -n > guards


    _______________________________________________________

Reply to this item at:

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

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