Providing decoded tx_data in reports

Description

Mythril reports vulnerable transaction sequences with corresponding argument values which may be included in tx_data. However, reports currently provide tx_data that is not decoded .

Therefore, if I want to test whether Mythril’s inputs work or not, it seems to I have to manually parse tx_data when multiple argument values exist in functions (transactions).

For the running example in README.md, an expected report format may be:

Caller: [CREATOR], constructor 
Caller: [CREATOR], killerize (0x....)
Caller: [CREATOR], activatekillability()
Caller: [CREATOR], commencekilling()

where we don’t need to parse tx_data anymore.

[norhh]

In my example, the constructor has only one input parameter which has uint type. I meant in general case when a constructor has multiple args. Look into solidity abi spec for more info https://solidity.readthedocs.io/en/develop/abi-spec.html

[SunBeomSo]

@norhh I have three additional questions.

But it takes some effort to extract the calldata into int, uint, address etc.

Could you provide any examples? What do you mean by int, uint, address etc ? In my example, the constructor has only one input parameter which has uint type.

Or do you have any relevant documents?

1. When dynamic arrays are passed into arguments (e.g., test function in my example), how can I know the size of the dynamic arrays from input field?