When generating a call graph, SPARK has to handle many special cases for concurrency helper classes like java.lang.Thread or android.os.AsyncTask. These classes usually have control flow properties hidden to the call graph analysis, e.g., the Thread's Thread.run method will be invoked asynchronously after calling Thread.start or AsyncTask.onPostExecute will be executed after `AsyncT

The memtrace* sample clients use drutil_expand_rep_string, but the instrace* ones do not. This can confuse users: https://groups.google.com/g/dynamorio-users/c/HR4pX6lwP_I

Wouldn't it be a good idea to create a simple introduction to the system, i.e. how to go from cloning the repo, to actually be able to analyze a file. This would be a great part, such that more people can use the framework.

Hello,

Thanks for this wonderful and powerfull program, and for sharing it with us.
I am in the process of testing it on a complexe symfony 4 application.
I would like to have report/result only on our bundles in src/, for instance src/MyBundle.
But this bundle depend of many classes in vendor/ and some other directory outside src/.

How can I set the anlaysis to covert reports only on `

Is your feature request related to a problem? Please describe.
Currently it is difficult to keep track of which tests are present and which should be implemented.
Describe the solution you'd like

• Given that it is a C++ project, it makes sense to use lcov