On Wed, Dec 14, 2016 at 1:23 AM, Peter Luschny <peter.lusc...@gmail.com> wrote: > Same problem as last time -- dead kernel: "The kernel has died, > and the automatic restart has failed." New message: > "Saving untrusted notebook". Untrusted notebook, what is this?
Hmm, that's too bad. Though it doesn't look like the *same* problem either. Last time there was an illegal instruction exception coming out of some NTL code. Now there's a presumably different illegal instruction in code that hasn't been wrapped in Cysignals. Sebastien reported what looks to be the same problem: ------------------------------------------------------------------------ Attaching gdb to process id 7632. Unable to start gdb (not installed?) GDB is not installed. Install gdb for enhanced tracebacks. ------------------------------------------------------------------------ Unhandled SIGILL: An illegal instruction occurred. This probably occurred because a *compiled* module has a bug in it and is not properly wrapped with sig_on(), sig_off(). Python will now terminate. ------------------------------------------------------------------------ Illegal instruction (core dumped) Could you tell me what kind of CPU you have? And remind me, was this running in a VM (it shouldn't matter but I'm curious)? The "untrusted notebook" message is just a normal part of IPython/Jupyter's security model and is nothing to do with Sage: http://jupyter-notebook.readthedocs.io/en/latest/security.html#security-in-notebook-documents -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
