Fix traceback parsing under Safari 6. #15
Closed
+113
−32
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
Safari (possibly just Safari 6) ends up in the Firefox traceback parser. This actually works with two minor fixes: - Function arguments are not supplied so don't attempt to parse them out. - Tracebacks appear to end in a '[native code]' entry. Deal with this.
|
Tests still fail on Safari 6 after applying c368a84. |
|
Fixed test in e18c7df and merged. |
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.
Safari (possibly just Safari 6) ends up in the Firefox traceback parser. This
actually works with two minor fixes: