Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using a sub-level debugger results in max recursion depth error #66

Open
jjmurre opened this issue Jul 9, 2024 · 2 comments
Open

Using a sub-level debugger results in max recursion depth error #66

jjmurre opened this issue Jul 9, 2024 · 2 comments

Comments

@jjmurre
Copy link

jjmurre commented Jul 9, 2024

When in a pdb debugger session, a new session (e.g. calling an arbitrary function foo) can be started with (Pdb+) debug foo().

However, this results in an error:

*** RecursionError: maximum recursion depth exceeded while calling a Python object
@mdmintz
Copy link
Owner

mdmintz commented Jul 9, 2024

Did the same issue occur with the original Pdb?

@jjmurre
Copy link
Author

jjmurre commented Jul 15, 2024

No, in the original pdb (or pdbpp) this does not happen. You get this reponse:

ENTERING RECURSIVE DEBUGGER
[1] > <string>(1)<module>()
((Pdb++)) 

So, the cursor gets kind-of "doubled".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants