Closed bababuck closed 7 months ago
Thanks for the report. I replicated the issue on my end, and I'll look into it.
This is indeed a bug. There's now a PR with a fix for it here: https://github.com/OpenCilk/productivity-tools/pull/41
This bug has been fixed in the latest release.
Describe the bug
Cilksan is reporting a race condition for when I free memory allocated by malloc. I have a small working example. My malloc/realloc/free manual specifies safe for multithreading:
Maybe it has to do with reuse of addresses by
malloc
afterfree
. I could also be wrong and this is a race condition, but I don't see how.Expected behavior
No race conditions detected.
OpenCilk version
Steps to reproduce (include relevant output)
cilksan.c