Fix "local type not allowed in final code: null_type" exception #235
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With IccTA enabled to detect ICC flows, when to instrument
onServiceConnected(ComponentName, IBinder)
for bound Service, aLocal
ofNullType
is created to represent the first argument of typeComponentName
. However,NullType
is not acceptable in the final Jimple code generated by Soot, when validating the body. Thus, an exception with the following message will be thrown:This simple fix replaces
NullType
with the correct typeComponentName
. Though even with this fix, FlowDroid still lacks the mechanism to detect ICC flows of bound Service, this fix can at least make sure FlowDroid finish its analysis without abnormal termination whenonServiceConnected(ComponentName, IBinder)
is used in the application code.You can validate this fix by running test on DroidBench app ServiceCommunication1.