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.

Sign up for GitHub

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

Error on must-relocking of non-recursive mutex #1628

Merged
merged 4 commits into from
Nov 29, 2024
Merged

Error on must-relocking of non-recursive mutex #1628

merged 4 commits into from
Nov 29, 2024

Commits on Nov 14, 2024

  1. Error on must-relocking of non-recursive mutex 

    mayLocks analysis can warn on it, but mutex analysis can be definite about it.
    @sim642
    sim642 committed Nov 14, 2024
    Configuration menu
    Copy the full SHA
    f2f0c12 View commit details
    Browse the repository at this point in the history

Commits on Nov 29, 2024

  1. Fix must-double-locking in regression tests

    @sim642
    sim642 committed Nov 29, 2024
    Configuration menu
    Copy the full SHA
    dbdefab View commit details
    Browse the repository at this point in the history

  2. Check must-double-locking in 03-practical/21-pfscan_combine_minimal

    @sim642
    sim642 committed Nov 29, 2024
    Configuration menu
    Copy the full SHA
    218770b View commit details
    Browse the repository at this point in the history

  3. Change must-double-locking in 03-practical/21-pfscan_combine_minimal … 

    …to TODO

On MacOS the mutex type is top because it's zero-initialized global.
On MacOS zero-initialized mutex isn't the same as a default mutex (type 0).
    @sim642
    sim642 committed Nov 29, 2024
    Configuration menu
    Copy the full SHA
    f3dfca7 View commit details
    Browse the repository at this point in the history