DynamoRIO / DynamoRIO/dynamorio

CRASH when processing large offline trace

Open
#6,854 2 comments 0 reactions 0 assignees View on GitHub
Bug-ToolCrash Component-DrMemtrace Status-NeedInfo
Dominant language
C
Stars
3.2k
Forks
629
Avg merge
2d 15h
Merged PRs (30d)
31

Description

On a powerful Linux version 5.15 server, Running CPU2017's:
`CPU/531.deepsjeng_r/exe/deepsjeng_r_base.mytest-m64`
with the test dataset:
`CPU/531.deepsjeng_r/data/test/input/test.txt`
Execution without drcachesim is done after 5 seconds, with drcachesim 2 minutes.
I generate an offline trace, no "special" parameters are used. In the raw folder is a single .lz4 file sized 12GB, decompressing manually yields 57GB. I use drcachesim's Linux binaries version 10.0.0 that can be downloaded from the site.
When running the cache simulator on the offline trace, after 10 minutes I get the following error:
`Failed to open drmemtrace.deepsjeng_r_base.mytest-m64.190612.5977.dir/trace/drmemtrace.deepsjeng_r_base.mytest-m64.190612.1075.trace.zip
Failed to initialize scheduler: Failed to open drmemtrace.deepsjeng_r_base.mytest-m64.190612.5977.dir/trace/drmemtrace.deepsjeng_r_base.mytest-m64.190612.1075.trace.zip
ERROR: failed to initialize analyzer: raw2trace failed: Failed to process file for thread 190612: Failed to close prior component`

Trying to parse the trace again immediately yields the error:
`
Failed to open drmemtrace.deepsjeng_r_base.mytest-m64.190612.5977.dir/trace/drmemtrace.deepsjeng_r_base.mytest-m64.190612.1075.trace.zip
Failed to initialize scheduler: Failed to open drmemtrace.deepsjeng_r_base.mytest-m64.190612.5977.dir/trace/drmemtrace.deepsjeng_r_base.mytest-m64.190612.1075.trace.zip
ERROR: failed to initialize analyzer
`
checking out the trace folder created, there is a .zip file sized 2.8GB. Trying to run unzip -l on it yields:
`Archive: drmemtrace.deepsjeng_r_base.mytest-m64.200403.7015.trace.zip
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of drmemtrace.deepsjeng_r_base.mytest-m64.200403.7015.trace or
drmemtrace.deepsjeng_r_base.mytest-m64.200403.7015.trace.zip, and cannot find drmemtrace.deepsjeng_r_base.mytest-m64.200403.7015.trace.ZIP, period.`

Would appreciate pointers, I assume this is some sort of bug relating to large traces. I can parse the traces from google's charlie folder, with the largest file being about 2GB compressed if I remember correctly. I can also compile my own cpp programs, instrument them and parse the trace.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.