-
Notifications
You must be signed in to change notification settings - Fork 8
Description
In the linked test program, there is a private data access in f()
, which propagates the data to its caller e()
, and from there up to main()
. Then main()
calls a()
, which calls b()
, etc. Data accesses in c()
and d()
should be allowed, since c()
is annotated as an ephemeral "mysandbox"
sandbox.
So, I expected SOAAP to report the following data flow:
f -> e -> main -> a -> b
In the SOAAP-generated JSON file, however, there are no such traces. I do get some correct information about the private accesses in a
, b
, f
and main
: in all four cases, the data source is correctly shown as line 10 (which is in f()
). However, there is no trace showing how the data propagates from f()
to b()
, and there is no indication at all of a private data access in e()
. Now, there might be a valid argument that e()
doesn’t “access” the private data, but it is definitely involved in conducting the data along the path to main()
, a()
and b()
.