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.

Sign up for GitHub

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

Jump to bottom

@debug_last_error(): interpret only frames from Base.stacktrace() #336

Open
cstjean opened this issue Oct 10, 2023 · 1 comment
Open

@debug_last_error(): interpret only frames from Base.stacktrace() #336

cstjean opened this issue Oct 10, 2023 · 1 comment

Comments

@cstjean
Copy link

cstjean commented Oct 10, 2023

Apologies if it's been suggested before, but because inspecting the stack of the last error is so useful, couldn't a macro like @debug_last_error() grab the last REPL command to hit an exception, then rerun it in the debugger, interpreting only those frames which are in Base.stacktrace()? I realize that this is non-trivial, but it would make execution fast enough in almost all cases...
@pfitzseb
Copy link
Member

Similar idea to JuliaDebug/Infiltrator.jl#99 (comment). This seems pretty straightforward to implement, I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pfitzseb @cstjean