[Octave-bug-tracker] [bug #56637] Access of a nested structure -> memory leak in mex function

[Mike Miller]

Follow-up Comment #8, bug #56637 (project octave):

In other words, we have a minimal example that doesn't show a memory leak. You
have a complex example that does show a memory leak. At the moment, it seems
most likely that the memory leak is in your code and not in Octave itself. As
the reporter, we hope that you will put in some more effort to reduce your
complex example to show a complete but minimal example that demonstrates the
leak. Or perhaps by attempting to do so you will discover the source of the
leak yourself. You might also try running your code under leak detection tools
like LeakSanitizer or Valgrind.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?56637>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/