I don't mean to close the bug, I just want to make sure the problem has a workaround that works for you.
As far as fixing this, I think there are really two bugs here: 1) An invalid value is being passed to an lapack routine, but I'm not sure if it's because your function is returning NaN under certain conditions or because of a bug in lapack. I see this with lapack version 3.4.2 (in Ubuntu 13.04) but not with version 3.4.1 (in 12.10). I will look more into this to see if it is worth reporting as a bug in lapack. 2) Octave already has a method for handling errors in the lapack routines like this one, but it is not working with the latest lapack library in Ubuntu 13.04. I've reported this to Octave upstream, but I'm not sure if anything can be done other than detect that lapack is built a certain way and that handling errors won't work as expected. Maybe better to turn this into a bug against the lapack packaging. -- 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
