I'm implementing a new kernel for jupyter notebooks and I need to trap segfaults occasionally and this notebook restarting behavior is getting in my way.
Best,
Christian Schafmeister
Professor
Chemistry Department
Temple University
Roland Weber
unread,
Nov 6, 2017, 2:23:22 AM11/6/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Project Jupyter
When debugging, you could change the KernelRestarter class. I'm not sure if it's configurable, but you certainly can hack the code. It's in the jupyter_client package.
hope that helps,
Roland
Matthias Bussonnier
unread,
Nov 6, 2017, 2:03:08 PM11/6/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jup...@googlegroups.com
I think you should be able to set `c.KernelRestarter.time_to_dead` to
an arbitrary large value. I don't think it allow infinity of negative
value to never consider the kernel dead, though if you are poking at
the code and want to submit a Pull-request to enable that I guess that
would be accepted.
Let us know of your experience in using LLDB to debug kernels.