Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

encounter a problem when running parseLogs() #1

Open
xianghl01 opened this issue Oct 16, 2024 · 0 comments
Open

encounter a problem when running parseLogs() #1

xianghl01 opened this issue Oct 16, 2024 · 0 comments

Comments

@xianghl01
Copy link

xianghl01 commented Oct 16, 2024

When I run analyzeOneTx on my own transaction trace generated from debug_traceTransaction, there is an error

File "/home/Trace2Inv-Artifact-FSE24/test.py", line 89, in analyzeOneTx
  metaTraceTree = p.parseLogs(name, contract, Tx, trace)
File "/home/Trace2Inv-Artifact-FSE24/parserPackage/parser.py", line 1103, in parseLogs
  metaTraceTree.updateInfoList("sstore", (key, value, pc), self.logging)
File "/home/Trace2Inv-Artifact-FSE24/parserPackage/traceTree.py", line 72, in updateInfoList
  self.internalCalls[-1].updateInfoList(key, value)
 IndexError: list index out of range

The output before encountering the error

read receipts stored on contract address:0xDD1803bE5710F6C1dFF99eEE16B5fFd7D4459fd1.txs
msg.data.size -> 0000000000000000000000000000000000000000000000000000000000000004 bytes
calldata[0000000000000000000000000000000000000000000000000000000000000000] -> d12cd94200000000000000000000000000000000000000000000000000000000
sload[0000000000000000000000000000000000000000000000000000000000000003] -> 0000000000000000000000d5e1731ee0dbc90865f7ec48ed17ecac8d44d19f01
caller -> 0x0000000000000000000000007b1f9eb78b870457039d094b8e4cfbe96eb30a
sload[0000000000000000000000000000000000000000000000000000000000000000] -> 000000000000000000000000007b1f9eb78b870457039d094b8e4cfbe96eb30a
sload[0000000000000000000000000000000000000000000000000000000000000003] -> 0000000000000000000000d5e1731ee0dbc90865f7ec48ed17ecac8d44d19f01
sstore[0000000000000000000000000000000000000000000000000000000000000003] = 0000000000000000000000d5e1731ee0dbc90865f7ec48ed17ecac8d44d19f02

Is there a problem with the trace?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant