Currently, the debugger looks up known (provided) bytecodes via observed binary values (via getCode or CREATE 0x...). These actual values are compared against the provided values using a naive string comparison. (For the case of CREATE, constructor arguments are truncated off word-by-word until there is a string match)
This PR modifies how that search is performed, and how the current context is represented:
Use regex search for bytecode, where the regex tolerates all values for link references. This assumes that link references are exactly 40 characters, either all 0s, or the __... syntax.
Override the reported "current context" value to use the actual binary, not the unresolved provided form.
Ref: #64
Currently, the debugger looks up known (provided) bytecodes via observed binary values (via
getCodeorCREATE 0x...). These actual values are compared against the provided values using a naive string comparison. (For the case ofCREATE, constructor arguments are truncated off word-by-word until there is a string match)This PR modifies how that search is performed, and how the current context is represented:
0s, or the__...syntax.