[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #58505] Handing NAs to glpk() can causes sever
|
From: |
Markus Mützel |
|
Subject: |
[Octave-bug-tracker] [bug #58505] Handing NAs to glpk() can causes several classes of crashes |
|
Date: |
Sun, 7 Jun 2020 05:57:19 -0400 (EDT) |
|
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0 |
Update of bug #58505 (project octave):
Status: None => Confirmed
Release: 5.2.0 => 6.0.90
Operating System: GNU/Linux => Any
_______________________________________________________
Follow-up Comment #1:
I can confirm the crashes here.
Since development for Octave 5 has stopped, I'm re-targeting the release to
version 6.
It is clear that Octave shouldn't segfault in any of these cases.
Since "glpk" is an Octave-only function, we can decide what the desired
behavior should be.
For the probably easier case with NaN input:
* Should Octave throw an error?
* Should the function return NaN? For all output arguments (errnum!)?
* Something else?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?58505>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/