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.

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

PISTON-1137: Fixes inaccurate stack trace. #6638

Conversation

tetrachromium
Copy link

If an exception is caught within the kvm_message:prepend_and_notify/5 function, the correct stack trace was potentially overwritten by an exception occuring within the kvm_message:remove_malform_vm/2 function. The stack trace is now captured before calling that function.

If an exception is caught within the `kvm_message:prepend_and_notify/5` function, the correct stack trace was potentially overwritten by an exception occuring within the `kvm_message:remove_malform_vm/2` function. The stack trace is now captured before calling that function.
jamesaimonetti pushed a commit that referenced this pull request Oct 12, 2020
If an exception is caught within the
`kvm_message:prepend_and_notify/5` function, the correct stack trace
was potentially overwritten by an exception occuring within the
`kvm_message:remove_malform_vm/2` function. The stack trace is now
captured before calling that function.
@jamesaimonetti
Copy link
Member

Merged

@tetrachromium tetrachromium deleted the PISTON-1137-fix-stack-trace-4.3-upstream branch October 20, 2020 23:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants