[Octave-bug-tracker] [bug #48793] no need for OCTAVE_LOCAL_BUFFER anymore

[Rik]

Update of bug #48793 (project octave):

                  Status:               Need Info => Confirmed              

    _______________________________________________________

Follow-up Comment #1:

I agree that we should use standard C++ features whenever possible rather than
rolling our own code.  It wasn't that hard, so I made two different
implementations of OCTAVE_LOCAL_BUFFER.  One is based on bytes, and one is
based on the passed in object type T.  Unfortunately, while they compile just
fine, the resulting binary segfaults.  I think what this really means is that
there are issues in Octave code around double frees of memory.  For reference,
I'm attaching the implementation.  

(file #41244)
    _______________________________________________________

Additional Item Attachment:

File name: local_buffer.patch             Size:12 KB


    _______________________________________________________

Reply to this item at:

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

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