Open joseluispino opened 9 years ago
% bin/symquery.exe -f -e dynamorio/lib32/release/dynamorio.dll -a 0xbe328
get_ldr_module_64+0x28
d:\drmemory_package\dynamorio\core\win32\module_shared.c:878+0x0
Do you have Norton Internet Security, and you're on Windows 8 or higher? This looks like #1685.
Looks the same... I will test again tomorrow after deactivating Norton. I an using Windows 8.
Thanks, Jose On Mar 15, 2015 10:01 AM, "derekbruening" notifications@github.com wrote:
% bin/symquery.exe -f -e dynamorio/lib32/release/dynamorio.dll -a 0xbe328 get_ldr_module_64+0x28 d:\drmemory_package\dynamorio\core\win32\module_shared.c:878+0x0
Do you have Norton Internet Security, and you're on Windows 8 or higher? This looks like #1685 https://github.com/DynamoRIO/drmemory/issues/1685.
— Reply to this email directly or view it on GitHub https://github.com/DynamoRIO/drmemory/issues/1690#issuecomment-81069148.
Could you try this build (it's a self-extracting archive, so unpack somewhere and run bin/drmemory from there) with Norton enabled?
http://build.chromium.org/p/client.drmemory/builds/DrMemory-Windows-1.8.16511-0x4b30da9-sfx.exe
Hi,
Thanks! The patch fixed the crash on our small unit tests... it did not fix the crash when I start my main application.
Best regards, Jose
Dr. Memory Notice:
Application
E:\tfs\SystemVue\DevelStable\vs2012_v110_SystemVue_Win32_Debug\Debug\bin\SystemVue.exe
(11068). Dr. Memory internal crash at PC 0x70e157f9. Please report this
at http://drmemory.org/issues. Program aborted.
0x80000001 0x00000000 0x70e157f9 0x70e157f9 0x00000001 0x420eee20
Base: 0x70dd0000
Registers: eax=0xffffffff ebx=0x00000003 ecx=0x420ef64c edx=0x7388791c
esi=0x00000270 edi=0x3dedb0c0 esp=0x420eee24 ebp=0x420ef624
eflags=0x000
version 5.0.16511, custom build
-no_dynamic_options -disasm_mask 8 -logdir
'C:\Users\jpino\AppData\Roaming\Dr. Memory\dynamorio' -client_lib
'C:\Program Files (x86)\Dr. Memory\bin\release\drmemorylib.dll;0;-logdir
C:\Users\jpino\AppData\Roaming\Dr. Memory
-symcache_dir
C:\Users\jpino\AppData\Roaming\Dr. Memory\symcache
-lib_blacklist
C:\windows*.d?? -resfile 11068 ' -code_api -probe_api -stack_size 56K -dis
0x420ef624 0x70e37fe8
0x420ef63c 0x73801c11
On Mon, Mar 16, 2015 at 9:37 PM, derekbruening notifications@github.com wrote:
Could you try this build (it's a self-extracting archive, so unpack somewhere and run bin/drmemory from there) with Norton enabled?
http://build.chromium.org/p/client.drmemory/builds/DrMemory-Windows-1.8.16511-0x4b30da9-sfx.exe
— Reply to this email directly or view it on GitHub https://github.com/DynamoRIO/drmemory/issues/1690#issuecomment-82102066.
It looks like the early-thread issue in #1685 is fixed, then. The new crash you've pasted is a different problem:
% bin/symquery -f -e dynamorio/lib32/release/dynamorio.dll -a 0x457f9 do_file_write+0x9 e:\b\build\slave\win-builder\drmemory\dynamorio\core\utils.c:1677+0x9 % bin/symquery -f -e bin/release/drmemorylib.dll -a 0x01c11 create_thread_logfile+0x61 e:\b\build\slave\win-builder\drmemory\drmemory\drmemory.c:514+0x52
0:000> U dynamorio+457f9-9 dynamorio!do_file_write [e:\b\build\slave\win-builder\drmemory\dynamorio\core\utils.c @ 1677]: 710457f0 55 push ebp 710457f1 8bec mov ebp,esp 710457f3 81ec00080000 sub esp,800h 710457f9 56 push esi 710457fa 8b7508 mov esi,dword ptr [ebp+8]
0x80000001 = STATUS_GUARD_PAGE_VIOLATION
This is odd, b/c create_thread_logfile() is called from event_thread_init(), which should be on a fresh dstack. Unless this is the early thread (though it's not clear why it would be different here than in smaller tests), which would be on initstack. Though its stack usage should exactly match the test suite test added for i#1685.
In any case, could you try running the new build with these options:
-dr_ops "-stack_size 128K"
?
Hi,
Thanks for the suggestion - I just tried with the arguments suggested and
Dr. Memory Notice:
Application
E:\tfs\SystemVue\DevelStable\vs2012_v110_SystemVue_Win32_Debug\Debug\bin\SystemVue.exe
(5184). Dr. Memory internal crash at PC 0x710257f9. Please report this at
http://drmemory.org/issues. Program aborted.
0x80000001 0x00000000 0x710257f9 0x710257f9 0x00000001 0x4212ee20
Base: 0x70fe0000
Registers: eax=0xffffffff ebx=0x00000003 ecx=0x4212f64c edx=0x7388791c
esi=0x00000274 edi=0x3df53a00 esp=0x4212ee24 ebp=0x4212f624
eflags=0x000
version 5.0.16511, custom build
-no_dynamic_options -disasm_mask 8 -logdir
'C:\Users\jpino\AppData\Roaming\Dr. Memory\dynamorio' -client_lib
'C:\Program Files (x86)\Dr. Memory\bin\release\drmemorylib.dll;0;-logdir
C:\Users\jpino\AppData\Roaming\Dr. Memory
-symcache_dir
C:\Users\jpino\AppData\Roaming\Dr. Memory\symcache
-lib_blacklist
C:\windows*.d?? -resfile 5184 ' -code_api -probe_api -stack_size 128K -dis
0x4212f624 0x71047fe8
0x4212f63c 0x73801c11
I kept doubling the stack size argument until I got to 1024K and it still failed.
Thanks, Jose
On Tue, Mar 17, 2015 at 11:19 AM, derekbruening notifications@github.com wrote:
It looks like the early-thread issue in #1685 https://github.com/DynamoRIO/drmemory/issues/1685 is fixed, then. The new crash you've pasted is a different problem:
% bin/symquery -f -e dynamorio/lib32/release/dynamorio.dll -a 0x457f9 do_file_write+0x9 e:\b\build\slave\win-builder\drmemory\dynamorio\core\utils.c:1677+0x9 % bin/symquery -f -e bin/release/drmemorylib.dll -a 0x01c11 create_thread_logfile+0x61 e:\b\build\slave\win-builder\drmemory\drmemory\drmemory.c:514+0x52
0:000> U dynamorio+457f9-9 dynamorio!do_file_write [e:\b\build\slave\win-builder\drmemory\dynamorio\core\utils.c @ 1677]: 710457f0 55 push ebp 710457f1 8bec mov ebp,esp 710457f3 81ec00080000 sub esp,800h 710457f9 56 push esi 710457fa 8b7508 mov esi,dword ptr [ebp+8]
0x80000001 = STATUS_GUARD_PAGE_VIOLATION
This is odd, b/c create_thread_logfile() is called from event_thread_init(), which should be on a fresh dstack. Unless this is the early thread (though it's not clear why it would be different here than in smaller tests), which would be on initstack. Though its stack usage should exactly match the test suite test added for i#1685.
In any case, could you try running the new build with these options: -dr_ops "-stack_size 128K"?
— Reply to this email directly or view it on GitHub https://github.com/DynamoRIO/drmemory/issues/1690#issuecomment-82508983.
I believe the the 0x80000001 issue is identical to #1723 which is now fixed. Could you try the latest build here:
http://build.chromium.org/p/client.drmemory/builds/DrMemory-Windows-1.8.16561-0x6500c42-sfx.exe