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

Walking up and down the call stack #3129

Closed
amelio-vazquez-reina opened this issue Apr 3, 2013 · 2 comments
Closed

Walking up and down the call stack #3129

amelio-vazquez-reina opened this issue Apr 3, 2013 · 2 comments
Milestone

Comments

@amelio-vazquez-reina
Copy link

I have been using IPython for a about a 1 - 1.5 years now, and I just read that IPython documentation says:

You can print variables, see code, execute statements and even walk up and down the call stack to track down the true source of the problem (which often is many layers in the stack above where the exception gets triggered).

How can I walk up and down the call stack when an error (exception) occurs?

Also, how can I do that also from an embedded shell?

@juliantaylor
Copy link
Contributor

The documentation tells you a few lines higher:
The %pdb command allows you to toggle on and off the automatic invocation of an IPython-enhanced pdb debugger

the debugger has the same commands as pdb, (up, down frame #number) see its documentation.

This is a question better suited for the ipython-user mailing list than the bug tracker, thus closing.

@Carreau
Copy link
Member

Carreau commented Apr 3, 2013

See also %debug that allow to do it post mortem.

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

3 participants