Question: Mechanism to automatically show N lines of context at each debugger-stop

[zachriggle]

I really like ipdb, which is built on and uses a lot of ipython features!

Unfortunately, some portion of ipdb or ipython does NOT like to play nice when embedded inside LLDB to debug LLDB Python scripts. Everything works the first time, then all Python is broken after that.

pdbpp on the other hand seems to work well! pdbpp has the sticky view which is REALLY cool, but overkill for some uses and detrimental for others (e.g. stepping over a print statement, you won't see the output).

Is there a way to configure pdbpp to show N lines of context before / after the current line, on every debugger stop? This is the equivalent of hitting l on each stop. I'm digging through the pdbpp internals now to sort it out, but I figured it was worth asking if it might save some time.

[blueyed]

There's no such option yet.
Try the master branch for fixes/improvements with regard to (not) hiding prints.

I could imagine that the option would be applied to sticky mode, where you then set the maximum context lines before/after/around the current line. Does that make sense?
Currently this is limited to the number of screen lines already, taking into account extra output via pdb's msg mechanism additionally.

[zachriggle]

I'm in the process of switching from ipdb (based on IPython) to pdb++ because the former breaks everything in LLDB.

ipdb has a nice option for lines-of-context-displayed-at-each-breakpoint-or-debugger-step, it would be nice to have this functionality in pdbpp.

[mdmintz]

This particular change would be helpful, as I am in the process of swapping ipdb with pdbpp (pdb++) in SeleniumBase. seleniumbase/SeleniumBase#1615