Skip to content

mutex as argument  #4

Description

@kheradmand

Strator has problems when it comes to mutexes as function argument. It will assume each function argument is a different mutex irrelevant of the path. this will cause problems in some situations. Both causes false negatives and false positives.
Solution is to write something like getDefOperand but flow-sensitive, and only for values that depend on only one other value (bitcasts, argument passings, ...)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions