You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The standard Python REPL isn't the most convenient for long debugging sessions. Specifically, editing multi-line blocks sucks, and reusing anything that you came up with for future debugging sessions is tedious. @htejun experimented with Jupyter and found that it is super useful in conjunction with drgn thanks to its persistent, reusable cells:
It's possible to wire up drgn and Jupyter together today, but we should explore integrating them more and documenting it.
One thing I’ve meant to do for awhile (but haven’t found the time) is to host a mini kernel core dump and its deubginfo alongside a Jupiter notebook showcasing drgn somewhere.
That way people can just open the notebook with Google Colab and jump straight into learning kernel debugging interactively.
The standard Python REPL isn't the most convenient for long debugging sessions. Specifically, editing multi-line blocks sucks, and reusing anything that you came up with for future debugging sessions is tedious. @htejun experimented with Jupyter and found that it is super useful in conjunction with drgn thanks to its persistent, reusable cells:
It's possible to wire up drgn and Jupyter together today, but we should explore integrating them more and documenting it.
The text was updated successfully, but these errors were encountered: