Add Support for Stack Traces #5
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The argument to the debug_setup handler now has some stack trace * SWANK sends the top n stack frames (20 by default) Created a function to fetch the full stack trace
|
As I mentioned in the related pull request for atom slime, I added more functionality than just printing stack frames. Unlike the atom slime pull request though, this has (untested) hooks for stepping. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds support for fetching stack traces when debugging. Swank already sends the top few frames (20 by default), so this adds the information passed to the debug setup handler. Additionally, this provides a function to fetch the full stack trace.