[Octave-bug-tracker] [bug #40739] Attempt to allocate (size_t)-1 bytes when trying to length-INT_MAX create sparse vector

[Rik]

Update of bug #40739 (project octave):

                  Status:                    None => Confirmed              

    _______________________________________________________

Follow-up Comment #3:

Confirmed.  I didn't use an address sanitizer and the behavior seems to be
that Octave really does try and allocate 2^31-1 entries; This threw my
computer into a swap disaster and I was lucky to be able to get to a shell
prompt eventually and kill the process.

    _______________________________________________________

Reply to this item at:

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

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