search

cuplv / TraceRunner

Tool for generating dynamic traces of android applications.
3 stars 0 forks source link

Dropping messages #38

Closed ftc closed 7 years ago

ftc commented 7 years ago

Messages from the TraceRunnerRuntimeInstrumentation are occasionally dropped when running from the monkey script. So far I have not found any pattern to it and I believe it is OK to use the trace if callback-verification reads it since it checks for matching entry/exits. It is possible if multiple messages in a row are dropped then we could lose an entire callback however I have not seen more than one dropped in a row. Most of the time it is something which gets filtered out anyway so it doesn't affect the overall verification.

To check if more than one message is missing run the following script:

python TraceRunner/utils/ProtoConverter/pro
toPrinter.py --trace $f --check on

@smover @sllam please take a look at this issue and make sure this seems like a reasonable thing to do.

ftc commented 7 years ago

I fixed a minor bug in the TraceRunnerRuntimeInstrumentation and added logcat output to catch some things that may be going wrong. Lets just run it again and see how it works.

ftc commented 7 years ago

Sorting messages seems to make the remaining messages sequential. Closing issue.