4:37:54Kevslingerdrmeister: Perhaps this is all we need https://github.com/QuantStack/xwidgets
4:38:18KevslingerIt's the C++ backend for the Jupyter widgets
4:39:36KevslingerXeus (what we were calling Xenon or Xeon or whatever today) seems to be a new, lightweight IpyKernel. They have a python and C++ implementation currently
13:45:55drmeisterIt's on the stack - but we don't have anything yet to view c++ source.
13:47:41drmeisterThis is going to help tremendously with debugging once other people start hitting these.
13:48:15drmeisterI should use (core:safe-backtrace) when we get a SEGMENTATION-VIOLATION in jupyter notebooks - then it would show the C++ functions as well.
13:48:48drmeisterBut just touching restricted memory is not the end of everything.
13:51:10davidlovemoreIn one ARM JIT I worked on, we used to regularly BL (Branch and link) to 0 conditionally to generate an error as part of debugging. Brings back memories.
13:52:43Bikeactually no, guess it only provides the instruction's address
13:54:16selwyndrmeister: do your collaborators prefer to develop with jupyter notebooks over emacs?
13:54:43davidlovemoreThe address should be on the stack. You can definitely get at the registers after a fault. The MPS code does this. The return address should be in [rsp].
13:55:26drmeisterselwyn: They will - yes. I also prefer it because I use it to interactively debug complex things like geometry optimization.
13:55:45drmeisterselwyn: We connect a slime session into the jupyter notebook - so we get the best of both worlds.