Feature #11839
closedGet rid of implicit resources
0%
Description
There are just 2 environment model specifications that implicitly refer resources in the following manner:
"resource": {
"resource": true
}
It seems to confuse EMG in some cases when allocating memory for corresponding actual resources and passing them to callbacks. Let's to refer all resources explicitly.
Updated by Evgeny Novikov about 2 years ago
- Blocks Feature #11810: Check whether the same resources are passed to various related callbacks added
Updated by Evgeny Novikov about 2 years ago
- Status changed from New to Resolved
I fixed the issue in branch get-rid-of-implicit-resources that is tested right now.
Updated by Evgeny Novikov about 2 years ago
- Status changed from Resolved to Closed
CI passed tests without any regressions while verification of a subset of Linux kernel drivers demonstrated some changes. First of all, 6 of 8 failures of EMG have gone, so now 6 more drivers are verified. Besides, it seems that now the verification tool can reveal better some other drawbacks of appropriate environment model specifications, namely, usb_serial. I merged the branch to master in e48156110.