Open ivankyluk opened 3 weeks ago
When the same test ran in vs2019-32, it crashed with the following error:
133: Test command: D:\a\dynamorio\dynamorio\build_debug-internal-32\bin32\drrun.exe "-s" "90" "-quiet" "-debug" "-use_dll" "D:/a/dynamorio/dynamorio/build_debug-internal-32/lib32/debug/dynamorio.dll" "-exit0" "-stderr_mask" "0xC" "-msgbox_mask" "0" "-dumpcore_mask" "0x7d" "-staged" "-code_api" "-c" "D:/a/dynamorio/dynamorio/build_debug-internal-32/suite/tests/bin/client.memory_dump_test.dll.dll" "--" "D:/a/dynamorio/dynamorio/build_debug-internal-32/suite/tests/bin/simple_app.exe" 133: Working Directory: D:/a/dynamorio/dynamorio/build_debug-internal-32/suite/tests 133: Test timeout computed to be: 120 134: Test timeout computed to be: 120 133: thank you for testing memory dump 133: thread init 133: nudge delivered 1 133: <Application D:\a\dynamorio\dynamorio\build_debug-internal-32\suite\tests\bin\simple_app.exe (7132). Tool internal crash at PC 0x7153e658. Please report this at your tool's issue tracker. Program aborted. 133: 0xc0000005 0x00000000 0x7153e658 0x7153e658 0x00000000 0x00000000 133: Base: 0x71470000 133: Registers: eax=0x00000000 ebx=0x1a2ab610 ecx=0x00000001 edx=0x1a1f18c0 133: esi=0x71902e6c edi=0x1a2ab608 esp=0x1a2abde8 ebp=0x1a2abdf4 133: eflags=0x00010202 133: version 11.0.20033, custom build 133: -no_dynamic_options -client_lib 'D:\a\dynamorio\dynamorio\build_debug-internal-32\suite\tests\bin\client.memory_dump_test.dll.dll;0;' -client_lib32 'D:\a\dynamorio\dynamorio\build_debug-internal-32\suite\tests\bin\client.memory_dump_test.dll.dll;0;' -code_api -probe_api -dumpcore_mask 125 -stderr_mask 12 -stack_size 56K 133: 0x1a2abdf4 0x71520853 133: 0x1a2abf1c 0x7151eb74 133: 0x1a2abff4 0x716f3bf4 133: 0x1a2ab640 0x7173a61f 133: 0x1a2ab688 0x1a2ab938 133: 0x1a2ab988 0x00000000 133: 0x0001007f 0x36e9773c> 132/266 Test #133: code_api|client.memory_dump_test .............................***Failed
7047 adds X86 Linux support to dr_create_memory_dump(). The PR also adds a test to cover WIN32 and X64.
When the same test ran in vs2019-32, it crashed with the following error:
133: Test command: D:\a\dynamorio\dynamorio\build_debug-internal-32\bin32\drrun.exe "-s" "90" "-quiet" "-debug" "-use_dll" "D:/a/dynamorio/dynamorio/build_debug-internal-32/lib32/debug/dynamorio.dll" "-exit0" "-stderr_mask" "0xC" "-msgbox_mask" "0" "-dumpcore_mask" "0x7d" "-staged" "-code_api" "-c" "D:/a/dynamorio/dynamorio/build_debug-internal-32/suite/tests/bin/client.memory_dump_test.dll.dll" "--" "D:/a/dynamorio/dynamorio/build_debug-internal-32/suite/tests/bin/simple_app.exe" 133: Working Directory: D:/a/dynamorio/dynamorio/build_debug-internal-32/suite/tests 133: Test timeout computed to be: 120 134: Test timeout computed to be: 120 133: thank you for testing memory dump 133: thread init 133: nudge delivered 1 133: <Application D:\a\dynamorio\dynamorio\build_debug-internal-32\suite\tests\bin\simple_app.exe (7132). Tool internal crash at PC 0x7153e658. Please report this at your tool's issue tracker. Program aborted. 133: 0xc0000005 0x00000000 0x7153e658 0x7153e658 0x00000000 0x00000000 133: Base: 0x71470000 133: Registers: eax=0x00000000 ebx=0x1a2ab610 ecx=0x00000001 edx=0x1a1f18c0 133: esi=0x71902e6c edi=0x1a2ab608 esp=0x1a2abde8 ebp=0x1a2abdf4 133: eflags=0x00010202 133: version 11.0.20033, custom build 133: -no_dynamic_options -client_lib 'D:\a\dynamorio\dynamorio\build_debug-internal-32\suite\tests\bin\client.memory_dump_test.dll.dll;0;' -client_lib32 'D:\a\dynamorio\dynamorio\build_debug-internal-32\suite\tests\bin\client.memory_dump_test.dll.dll;0;' -code_api -probe_api -dumpcore_mask 125 -stderr_mask 12 -stack_size 56K 133: 0x1a2abdf4 0x71520853 133: 0x1a2abf1c 0x7151eb74 133: 0x1a2abff4 0x716f3bf4 133: 0x1a2ab640 0x7173a61f 133: 0x1a2ab688 0x1a2ab938 133: 0x1a2ab988 0x00000000 133: 0x0001007f 0x36e9773c> 132/266 Test #133: code_api|client.memory_dump_test .............................***Failed