-
Notifications
You must be signed in to change notification settings - Fork 41
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
Static field accesses is not properly modeled #97
Comments
Make sure to check out the examples given in #163 and eclipse-cognicrypt/CogniCrypt#292 when working on this issue. |
Signed-off-by: Rakshit Krishnappa Ravi <[email protected]> - generates seed for assignment statements with static field from CrySL ruleclass - fixed ensuresPred method to handle seeds with static field assignment
Current solution: Determine the actual method used for initialising the static field. If the method is an initial transition, then the seed is generated for the original statement that has the static field. Roadblock: The above solution requires the body of the initialiser method (
Alternate solution : Retrieve the body of the initialiser method ( |
The data-flow of a static field is not correctly detected.
The test case below succeeds
whereas when we replace it to the equivalent usage of (
AES128_GCM
is instantiated via a call tocreateAesGcmKeyTemplate
)The predicate does not reach the assertion
The text was updated successfully, but these errors were encountered: