octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #57284] Crash in MEX file when outputs are not


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #57284] Crash in MEX file when outputs are not used
Date: Thu, 21 Nov 2019 12:13:38 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Follow-up Comment #11, bug #57284 (project octave):

I think the +2 result is happening because of padding or alignment or luck.

We do have to allocate at least one output so that a function that produces
one output but is called with none will work and allow assignment to ans.

Since we are only talking about allocating an array of pointers, we could
allocate a minimum of 32 and it would just cost 256 bytes per function call. 
I don't think that's much considering the size of user-define function objects
(for example).


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]