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
Semantics of EXIT message delivery is broken. #303
Comments
This seems indeed to be a bug. I mistakenly thought that this was not a valid issue when I closed #102, but the justification given there is wrong. Thank you very much for the report and the test! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The documentation for erlang:unlink/1 function states the following:
So if a process A with trap_exit set to true unlinks from a process B and then makes sure to clean up an EXIT message from B that might have been put into the mailbox before the call to unlink, it should be protected from seeing this EXIT message in the future. Concuerror doesn't seem to adhere to this semantics.
To Reproduce
Run Concuerror on the following module:
Concuerror reports an error:
Expected behavior
According to my reading of erlang:unlink/1 documentation this code is fine and no error should be reported.
The text was updated successfully, but these errors were encountered: