To sum up, the crash in Octave is unfortunate and should be fixed, but the system of equations that you are feeding fsolve is a contributing factor. Your function f(x) is not well-defined over all values of x, for example
octave:1> x = [0;0;0]; octave:2> f(x) ABNORMAL RETURN FROM DQAGI ABNORMAL RETURN FROM DQAGI ABNORMAL RETURN FROM DQAGI ans = NaN NaN NaN With the second set of parameters, I can verify that the crash occurs as a NaN value is being passed into a LAPACK function that does not behave well when one of its arguments is a NaN. So in addition to the fix I suggested above, you could also ensure your function returns real values for all reasonable input values to avoid passing bad arguments into the library routines used by Octave. Do these suggestions resolve this issue for you? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156575 Title: octave crashed with SIGABRT in __libc_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octave/+bug/1156575/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
