Support for location included in stack traces in Erlang R15 #52
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
|
Shouldn't the inserted tuple be |
ghost
assigned
eproxus
added a commit
that referenced
this pull request
Jan 12, 2012
Support for location included in stack traces in Erlang R15
|
Spoke with the Erlang/OTP team and Erlang should be able to handle the 3-tuples still in all exception code. It's possible to get the line numbers and file name from the abstract code and I'll see if I can add this to the code so those fields could be filled in too. In either case, this patch will fix the failing tests for no |
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.
Support added in the meck:inject/4 function and the unit tests to support the new [{file,},{line,}] information included in stack traces