raw2trace WARNING while processing trace collected with -trace_after_instrs and -trace_for_instrs
Describe the bug I am tracing threadsig.cpp (from https://raw.githubusercontent.com/DynamoRIO/drmemtrace_samples/master/threadsig.x86_64/threadsig.cpp). I am seeing the warning shown below while running raw2trace.
$ build/clients/bin64/drraw2trace -jobs 1 -indir drmemtrace.threadsig.200649.7844.dir/
WARNING: Input file for thread 200651 is truncatedTo Reproduce
$ build/bin64/drrun -t drcachesim -trace_after_instrs 2000M -trace_for_instrs 10K -verbose 0 --offline -- ./threadsig 2 20000000
<Starting application /home/prasun/dynamorio-latest/threadsig (200649)>
<Initial options = -no_dynamic_options -client_lib '/home/prasun/dynamorio-latest/build/bin64/../clients/lib64/debug/libdrmemtrace.so;0;-trace_after_instrs 2000M -trace_for_instrs 10K -verbose 0 --offline' -client_lib64 '/home/prasun/dynamorio-latest/build/bin64/../clients/lib64/debug/libdrmemtrace.so;0;-trace_after_instrs 2000M -trace_for_instrs 10K -verbose 0 --offline' -code_api -stack_size 56K -signal_stack_size 32K -max_elide_jmp 0 -max_elide_call 0 -early_inject -emulate_brk -no_inline_ignored_syscalls -native_exec_default_list '' -no_native_exec_managed_code -no_indcall2direct >
<Paste into GDB to debug DynamoRIO clients:
set confirm off
add-symbol-file '/home/prasun/dynamorio-latest/build/bin64/../clients/lib64/debug/libdrmemtrace.so' 0x00007f79af2973c0
add-symbol-file '/home/prasun/dynamorio-latest/build/lib64/debug/libdynamorio.so' 0x00007f79f34cd780
add-symbol-file '/home/prasun/dynamorio-latest/build/ext/lib64/debug/libdrsyms.so' 0x00007f79af525260
add-symbol-file '/lib/x86_64-linux-gnu/libc.so.6' 0x00007f79f2e84360
add-symbol-file '/lib64/ld-linux-x86-64.so.2' 0x00007f79f2c36f10
add-symbol-file '/home/prasun/dynamorio-latest/build/ext/lib64/debug/libdrwrap.so' 0x00007f79af76d6d0
add-symbol-file '/home/prasun/dynamorio-latest/build/ext/lib64/debug/libdrmgr.so' 0x00007f79af97e090
add-symbol-file '/home/prasun/dynamorio-latest/build/ext/lib64/debug/libdrutil.so' 0x00007f79afb8d850
add-symbol-file '/home/prasun/dynamorio-latest/build/ext/lib64/debug/libdrstatecmp.so' 0x00007f79afd937b0
add-symbol-file '/home/prasun/dynamorio-latest/build/ext/lib64/debug/libdrcovlib.so' 0x00007f79aff99e60
add-symbol-file '/home/prasun/dynamorio-latest/build/ext/lib64/debug/libdrx.so' 0x00007f79b01a6350
add-symbol-file '/home/prasun/dynamorio-latest/build/ext/lib64/debug/libdrreg.so' 0x00007f79b03b9010
add-symbol-file '/home/prasun/dynamorio-latest/build/ext/lib64/debug/libdrbbdup.so' 0x00007f79b05c8330
add-symbol-file '/home/prasun/dynamorio-latest/build/ext/lib64/debug/libdrpttracer.so' 0x00007f79b07d5130
add-symbol-file '/usr/lib/x86_64-linux-gnu/libsnappy.so.1' 0x00007f79f2a2f1b0
add-symbol-file '/usr/lib/x86_64-linux-gnu/libstdc++.so.6' 0x00007f79f26bb9c0
add-symbol-file '/lib/x86_64-linux-gnu/libm.so.6' 0x00007f79f228ba80
add-symbol-file '/lib/libgcc_s.so.1' 0x00007f79f2069b50
add-symbol-file '/lib/x86_64-linux-gnu/libz.so.1' 0x00007f79f1e4af90
>
<curiosity: rex.w on OPSZ_6_irex10_short4!>
<(1+x) Handling our fault in a TRY at 0x00007f79f3734199>
Hit delay threshold: enabling tracing.
Hit tracing window #0 limit: disabling tracing.
<dropping 3rd pending alarm signal>
Estimation of pi is 3.141592653589820
Received 8200 alarms
<Stopping application /home/prasun/dynamorio-latest/threadsig (200649)>Please also answer these questions:
- What happens when you run without any client?
- Not applicable since the issue is with the drcachesim client, but the program runs fine without any client
- What happens when you run with debug build ("-debug" flag to drrun/drconfig/drinject)?
- This was run with debug build. I didn't try the release build
Expected behavior No warning expected.
Screenshots or Pasted Text
Versions
- What version of DynamoRIO are you using?
- Does the latest build from https://github.com/DynamoRIO/dynamorio/releases solve the problem?
- No
- What operating system version are you running on? ("Windows 10" is not sufficient: give the release number.)
- Ubuntu 18.04.6 LTS
- Is your application 32-bit or 64-bit?
- 64-bit
Additional context Add any other context about the problem here.