JuliaDebug / JuliaDebug/Debugger.jl
`@debug_last_error()`: interpret only frames from `Base.stacktrace()`
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 514
- Forks
- 50
- Avg merge
- 9d 9h
- Merged PRs (30d)
- 1
Description
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...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by examining the proposed @debug_last_error() flow around the last REPL command, the debugger, and Base.stacktrace(); done means the macro can rerun the failing command while interpreting only the relevant stack frames.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100