Backtrace in comment #6 is irrelevant. It is expected and normal. The
JVM, started by Scilab, triggers on purpose 5 or 6 segfault on startup.
Continue in gdb a few time is the way to get the actual segfault.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311905

Title:
  scilab-bin crashed with SIGABRT in __GI_raise()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1311905/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to