Skip to content

Error in interpreting the packed binary data in ExecutionTracer.dat #475

@Jizhou-Chen

Description

@Jizhou-Chen

Hi, I have been strictly following the guide to get familiar with recording basic traces. http://s2e.systems/docs/Howtos/ExecutionTracers.html

As I ran s2e execution_trace test on the code given by the guide, I got the following:

WARNING: [execution_trace] Could not parse entry 38 in file /mnt/data/user/s2e/projects/test/s2e-last/ExecutionTracer.dat (unpack requires a buffer of 8 bytes)

WARNING: [analyzer] Section already loaded: name: rt_base=0x7fdae0a0f000 size=0x1b50 - module Module name:ld-linux-x86-64.so.2 (/lib64/ld-linux-x86-64.so.2) pid:2053

WARNING: [analyzer] Section already loaded: name: rt_base=0x7fdae0a11000 size=0x29335 - module Module name:ld-linux-x86-64.so.2 (/lib64/ld-linux-x86-64.so.2) pid:2053

WARNING: [analyzer] Section already loaded: name: rt_base=0x7fdae0a3b000 size=0xaee4 - module Module name:ld-linux-x86-64.so.2 (/lib64/ld-linux-x86-64.so.2) pid:2053

WARNING: [analyzer] Section already loaded: name: rt_base=0x7fdae0a47620 size=0x2af0 - module Module name:ld-linux-x86-64.so.2 (/lib64/ld-linux-x86-64.so.2) pid:2053

SUCCESS: [execution_trace] Execution trace saved to /mnt/data/user/s2e/projects/test/s2e-last/execution_trace.json

I tried the same procedures on another program written by myself and got the same "unpack requires a buffer of 8 bytes" error too.

As I looked up online, the issue seems to be caused by buggy implementation in interpreting the packed binary data in ExecutionTracer.dat

I'm currently looking into s2e-env/build/lib/s2e_env/commands/execution_trace.py and trying to find the root cause.

If anyone is familiar with this part, please feel free to shed a light on the issue. Thank you in advance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions