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

Non-racing: exit vs erlang:get_stacktrace #124

Closed
aronisstav opened this issue Jan 16, 2017 · 0 comments
Closed

Non-racing: exit vs erlang:get_stacktrace #124

aronisstav opened this issue Jan 16, 2017 · 0 comments
Labels
bug Issues where the tool is not behaving according to expectations.

Comments

@aronisstav
Copy link
Member

Following module produces a warning in 3c15bbb:

-module(stacktrace_vs_exit).

-export([test/0]).

test() ->
  spawn(fun() -> erlang:get_stacktrace() end).

Warning:

Warning: The following pair of instructions is not explicitly marked as non-racing in Concuerror's internals:
  1) exits normally
  2) [] = erlang:get_stacktrace()
 Please notify the developers to add info about this pair.
 Concuerror treats such pairs as racing (--assume_racing). (No other such warnings will appear)

This is necessarily in different processes and should be marked as non-racing.

@aronisstav aronisstav added bug Issues where the tool is not behaving according to expectations. help wanted Issues that anyone could start working on. An invitation to the community. labels Jan 16, 2017
@aronisstav aronisstav removed the help wanted Issues that anyone could start working on. An invitation to the community. label Jan 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues where the tool is not behaving according to expectations.
Projects
None yet
Development

No branches or pull requests

1 participant