Open TafThorne opened 8 years ago
I have just seen a refrence to: https://github.com/DynamoRIO/drmemory/wiki/Debugging posted in another bug. I will work through that tomorrow and report my findings here.
So the extra debug hased on that Debuggin link.
== Running with -dr_debug ==
~/DrMemory-Linux-1.10.1-3/bin/drmemory -dr_debug -- ./test -v Base32
<Starting application /home/thomasthorne/work/avon-uno/vtss_appl/ces/test/test (25742)>
<Paste into GDB to debug DynamoRIO clients:
set confirm off
add-symbol-file '/home/thomasthorne/DrMemory-Linux-1.10.1-3/bin64/release/libdrmemorylib.so' 0x000000007381c000
add-symbol-file '/home/thomasthorne/DrMemory-Linux-1.10.1-3/dynamorio/lib64/debug/libdynamorio.so' 0x000000007102d7d8
add-symbol-file '/usr/lib/x86_64-linux-gnu/libstdc++.so.6' 0x00007f0165694d20
add-symbol-file '/lib/x86_64-linux-gnu/libm.so.6' 0x00007f0165306600
add-symbol-file '/lib/x86_64-linux-gnu/libc.so.6' 0x00007f0164f568b0
add-symbol-file '/lib64/ld-linux-x86-64.so.2' 0x00007f0164d0eac0
add-symbol-file '/lib/x86_64-linux-gnu/libgcc_s.so.1' 0x00007f0164af9a70
>
<Initial options = -no_dynamic_options -logdir '/home/thomasthorne/DrMemory-Linux-1.10.1-3/drmemory/logs/dynamorio' -client_lib '/home/thomasthorne/DrMemory-Linux-1.10.1-3/bin64/release/libdrmemorylib.so;0;-logdir `/home/thomasthorne/DrMemory-Linux-1.10.1-3/drmemory/logs` -symcache_dir `/home/thomasthorne/DrMemory-Linux-1.10.1-3/drmemory/logs/symcache` -resfile 25742 ' -code_api -stack_size 56K -disable_traces -no_enable_traces -max_elide_jmp 0 -max_elide_call 0 -max_bb_instrs 256 -no_shared_traces -bb_ibl_targets -bb_single_restore_prefix -no_shared_trace_ibl_routine -no_enable_reset -no_reset_at_switch_to_os_at_vmm_limit -reset_at_vmm_percent_free_limit 0 -no_reset_at_vmm_full -reset_at_commit_free_limit 0K -reset_every_nth_pending 0 -vm_size 262144K -early_inject -emulate_brk -no_inline_ignored_syscalls -native_exec_default_list '' -no_native_exec_managed_code -no_indcall2direct >
~~Dr.M~~ Dr. Memory version 1.10.1
~~Dr.M~~ (Uninitialized read checking is not yet supported for 64-bit)
<(1+x) Handling our fault in a TRY at 0x000055a911413d1b>
<spurious rep/repne prefix @0x00007f01659a57f8 (f2 41 ff e3): >
<Invalid opcode encountered>
<Application /home/thomasthorne/work/avon-uno/vtss_appl/ces/test/test (25742). Dr. Memory internal crash at PC 0x000055a9113bc638. Please report this at http://drmemory.org/issues. Program aborted.
Received SIGSEGV at pc 0x000055a9113bc638 in thread 25742
Base: 0x000055a91115b000
Registers:eax=0x0000000000000000 ebx=0x0000000050b6bb52 ecx=0x0000000050611c60 edx=0x0000000000000000
esi=0x0000000000000000 edi=0x0000000000000000 esp=0x0000000050611a20 ebp=0x0000000050611b30
r8 =0x0000000000000000 r9 =0x0000000000000001 r10=0x000000000000006a r11=0x0000000000000246
r12=0x00007ffe3f3b6bc0 r13=0x00007ffe3f3b6f80 r14=0x00007ffe3f3b6e40 r15=0x0000000000000000
eflags=0x0000000000010202
1.10.1-3-(Apr 10 2016 18:07:52)0
-no_dynamic_options -disasm_mask 8 -logdir '/home/thomasthorne/DrMemory-Linux-1.10.1-3/drmemory/logs/dynamorio' -client_lib '/home/thomasthorne/DrMemory-Linux-1.10.1-3/bin64/release/libdrmemorylib.so;0;-logdir `/home/thomasthorne/DrMemory-Linux-1.10.1-3/drmemory/logs` -symcache_dir `/home/thomasthorne/DrMemory-Linux-1.10
0x0000000050611b30 0x000055a9113c00de
0x0000000050611cf0 0x000055a9113c0c4c
0x0000000050611d20 0x000055a91137dd83
0x0000000050611e50 0x000055a911380605
0x00000000506124a0 0x000055a911380cad
0x00000000506124e0 0x000055a91135cf24
0x0000000050612540 0x000055a911446e8a
0x0000000050612820 0x000055a91144b60d
0x0000000050612a20 0x000055a91144e084
0x0000000050612ab0 0x000055a911413952
0x00007ffe3f3b6b88 0x00000000007a9c30
0x00007f016431522e 0xfe894ce1894ce889>
== Run with other options == All the suggested options continued to reproduce the error for me. Running the 64 bit version also still generated an error message as follows:
$ ~/DrMemory-Linux-1.10.1-3/bin64/drmemory -- ./test -v Base32
~~Dr.M~~ Dr. Memory version 1.10.1
~~Dr.M~~ (Uninitialized read checking is not yet supported for 64-bit)
<Application /home/thomasthorne/work/avon-uno/vtss_appl/ces/test/test (26676). Dr. Memory internal crash at PC 0x0000556286de845f. Please report this at http://drmemory.org/issues. Program aborted.
Received SIGSEGV at pc 0x0000556286de845f in thread 26676
Base: 0x0000556286cfb000
Registers:eax=0x0000000000000000 ebx=0x0000000000000000 ecx=0x0000000053a71a90 edx=0x0000000053a71a88
esi=0x0000000000000000 edi=0x0000000000000000 esp=0x0000000053a71a20 ebp=0x0000000053a71a90
r8 =0x0000000000000000 r9 =0x0000556286ea3980 r10=0x0000000000000000 r11=0x0000556286e85060
r12=0x0000000053a71a88 r13=0x0000000000000002 r14=0x0000000053a71d40 r15=0x0000000000000000
eflags=0x0000000000010246
1.10.1-3-(Apr 10 2016 18:07:52)0
-no_dynamic_options -disasm_mask 8 -logdir '/home/thomasthorne/DrMemory-Linux-1.10.1-3/drmemory/logs/dynamorio' -client_lib '/home/thomasthorne/DrMemory-Linux-1.10.1-3/bin64/release/libdrmemorylib.so;0;-logdir `/home/thomasthorne/DrMemory-Linux-1.10.1-3/drmemory/logs` -symcache_dir `/home/thomasthorne/DrMemory-Linux-1.10
0x0000000053a71a90 0x00010401000c0000>
Let me know if there are any other diagnosis steps you would like me to perform. I cannot send you the binary under test or the code to generate it as they belong to my employer.
I have been asked to report the following:
So there it is. I guess 64-bit support might still need a bit of work. I will try and recompile my application in 32-bit tomorrow.