[Octave-bug-tracker] [bug #61472] AddressSanitizer crash in MEX tests

[John W. Eaton]

Follow-up Comment #30, bug #61472 (project octave):

Markus: Yes, the changes you made did help. thanks.  I think it was fixing the
declarations for octave_int<T>.  I have some more pending changes for
range<T>, MArray<T>, and intNDArray<T>.  There are probably a few others that
also need to be fixed but none of these other changes appear to be necessary
to fix the visibility problems.

I'll look at enabling the polymorphic allocator only if we are using a
compiler that claims to be C++17 actually supports the feature and otherwise
falling back on copying complex objects otherwise.  I can also make copying an
option for non-class objects, though I think it should be OK to mix malloc
with delete for those.  If it causes trouble on actual systems, users can
disable it.

    _______________________________________________________

Reply to this item at:

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

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