internal crash in Dr Strace windows version

[sltTn]

Hello
I am using DrStrace but an internal crash has occurred.
I attached the picture of the crash and the result,
Thanks in advance

Versions

• What version of Dr Memory are you using? DrMemory-Windows-2.3.0-1

• What operating system version are you running on? windows 10 education, 2019 Microsoft corporation

• Is your application 32-bit or 64-bit? 64 bit, X64

[derekbruening]

Without more information there's not much that can be done. It looks like you've deleted all the questions that were helping to provide that information? I'm not sure what can be expected to be done when there's no information on how to reproduce, whether this happens with any app such as hello,world on this machine or is limited to calc, what was being done with calc at the time, etc.

[sltTn]

I am using the new version of drstarce : DrMemory-Windows-1.11.17622-1

but this warning happens
WARNING: fetching symbol information (procedure may take some time).
WARNING: symbol fetching failed. Symbol lookup will be disabled.
ASSERT FAILURE: ....\drstrace\drstrace.c:670: false (drsys failed to init)

how can I gent the result from drstrace through windows 10?
thanks in advance

[derekbruening]

What Windows version is that? No, "Windows 10" is not enough: that's like just saying "Windows" these days. Each every-6-month release is a major upgrade, as big as Windows 8.1 to Windows 10 from the perspective of DrStrace.

As you see, it failed to get symbols, which means it won't have system call numbers. Did you try running with -verbose 3 to try to figure out why it failed? Is this like #2232? Probably it is not the same as the crash in the initial filing here.

[sltTn]

the version of windows 10 enterprise is 1809 and the system type is 64bit x-64 based processor.
and another question is about extracting system calls in a group.
in other words, how can I extract a system calls from a folder( a batch of files)? is it possible with drstrace??

In general, How can I extract System calls?? drstarce or Drmemory ?? what is the best way?
thanks in advance

[sltTn]

Also, after using Drmemory this result without system calls happens :
Dr. Memory version 1.11.17622 build 1 built on Apr 3 2018 15:23:07
Dr. Memory results for pid 9812: "calc.exe"
Application cmdline: "calc.exe"
Recorded 115 suppression(s) from default C:\Users\10\Downloads\DrMemory-Windows-1.11.17622-1\DrMemory-Windows-1.11.17622-1\bin64\suppress-default.txt

WARNING: application is missing line number information.

===========================================================================
FINAL SUMMARY:

DUPLICATE ERROR COUNTS:

SUPPRESSIONS USED:

NO ERRORS FOUND:
0 unique, 0 total unaddressable access(es)
0 unique, 0 total invalid heap argument(s)
0 unique, 0 total GDI usage error(s)
0 unique, 0 total handle leak(s)
0 unique, 0 total warning(s)
0 unique, 0 total, 0 byte(s) of leak(s)
0 unique, 0 total, 0 byte(s) of possible leak(s)
ERRORS IGNORED:
81 potential error(s) (suspected false positives)
(details: C:\Users\10\Downloads\DrMemory-Windows-1.11.17622-1\DrMemory-Windows-1.11.17622-1\drmemory\logs\DrMemory-calc.exe.9812.000\potential_errors.txt)
46 potential leak(s) (suspected false positives)
(details: C:\Users\10\Downloads\DrMemory-Windows-1.11.17622-1\DrMemory-Windows-1.11.17622-1\drmemory\logs\DrMemory-calc.exe.9812.000\potential_errors.txt)
940 unique, 1227 total, 293933 byte(s) of still-reachable allocation(s)
(re-run with "-show_reachable" for details)
Details: C:\Users\10\Downloads\DrMemory-Windows-1.11.17622-1\DrMemory-Windows-1.11.17622-1\drmemory\logs\DrMemory-calc.exe.9812.000\results.txt

[derekbruening]

Please use the users list https://groups.google.com/forum/#!forum/DrMemory-Users for general questions, as it will reach a wider audience of people who might have an answer, and it will reach other users who may find the information beneficial. The issue tracker is for specific detailed bugs. This issue was filed about a crash, and then a post about failing to initialize and acquire symbols was added which should likely be a separate issue: was the crash resolved? Was the symbol acquisition resolved??

[sltTn]

unfortunately, not yet, I cannot solve the crash, I told you the windows version but, how can I solve this??
after usage drmemory the above warning without result.

[derekbruening]

Repeating:
As you see, it failed to get symbols, which means it won't have system call numbers. Did you try running with -verbose 3 to try to figure out why it failed? Is this like #2232?

See #2232: probably this symbol fetch error should go under that issue, or a new issue, and not this issue which you filed about a crash.

after usage drmemory the above warning without result.

drmemory found no memory bugs in calc: sounds like what you would expect. Looks normal. Did you expect it to find a lot of bugs?

[sltTn]

thanks, I have gotten the answer because I was trying to extract system calls through drmemory while it finds bugs.

but about drstarce, there are still some warning.
the result of -verbose 3 is here:

C:\Users\10\Downloads\DrMemory-Windows-1.11.17622-1\DrMemory-Windows-1.11.17622-1\bin64>drstrace -verbose 3 -- calc
WARNING: fetching symbol information (procedure may take some time).
WARNING: symbol fetching failed. Symbol lookup will be disabled.
ASSERT FAILURE: ....\drstrace\drstrace.c:670: false (drsys failed to init)

also, the result of -verbose 1:
C:\Users\10\Downloads\DrMemory-Windows-1.11.17622-1\DrMemory-Windows-1.11.17622-1\bin64>drstrace -verbose 1 -- calc
WARNING: fetching symbol information (procedure may take some time).
WARNING: symbol fetching failed. Symbol lookup will be disabled.
ASSERT FAILURE: ....\drstrace\drstrace.c:670: false (drsys failed to init)

[derekbruening]

For one thing, you are running a very old, unsupported version 1.11.

[sltTn]

I have updated the new version into DrMemory-Windows-2.3.0-1 but still, there is something wrong:

WARNING: fetching symbol information (procedure may take some time).
System call information is missing for this operating system: WinVer=105;Rel=1903;Build=18362;Edition=Enterprise. Restarting to trigger auto-generation of system call information.
WARNING: Missing system call information for this operating system version.
Attempting to auto-generate system call information...
drsys_find_sysnum_libs: C:\WINDOWS\system32\ntdll.dll is readable
drsys_find_sysnum_libs: C:\WINDOWS\system32\kernelbase.dll is readable
drsys_find_sysnum_libs: C:\WINDOWS\system32\kernel32.dll is readable
drsys_find_sysnum_libs: C:\WINDOWS\system32\gdi32.dll is readable
drsys_find_sysnum_libs: C:\WINDOWS\system32\imm32.dll is readable
drsys_find_sysnum_libs: C:\WINDOWS\system32\user32.dll is readable
drsys_find_sysnum_libs: C:\WINDOWS\system32\win32u.dll is readable
drsys_find_sysnum_libs: C:\WINDOWS\system32\ntdll.dll is readable
drsys_find_sysnum_libs: C:\WINDOWS\system32\kernelbase.dll is readable
drsys_find_sysnum_libs: C:\WINDOWS\system32\kernel32.dll is readable
drsys_find_sysnum_libs: C:\WINDOWS\system32\gdi32.dll is readable
drsys_find_sysnum_libs: C:\WINDOWS\system32\imm32.dll is readable
drsys_find_sysnum_libs: C:\WINDOWS\system32\user32.dll is readable
drsys_find_sysnum_libs: C:\WINDOWS\system32\win32u.dll is readable
Symbol cache directory is "C:\Users\danagostar\Downloads\DrMemory-Windows-2.3.0-1\DrMemory-Windows-2.3.0-1\logs"
Fetching symbols for "C:\WINDOWS\system32\ntdll.dll", attempt #0
Successfully fetched or found symbols at "C:\Users\danagostar\Downloads\DrMemory-Windows-2.3.0-1\DrMemory-Windows-2.3.0-1\logs\symbols\wntdll.pdb\3D038F31BBBF51C701937460DBAB1F531\wntdll.pdb"
Fetching symbols for "C:\WINDOWS\system32\kernelbase.dll", attempt #0
Successfully fetched or found symbols at "C:\Users\danagostar\Downloads\DrMemory-Windows-2.3.0-1\DrMemory-Windows-2.3.0-1\logs\symbols\wkernelbase.pdb\00978E61DEFC5ED3BC6110BEE140815C1\wkernelbase.pdb"
Fetching symbols for "C:\WINDOWS\system32\kernel32.dll", attempt #0
Successfully fetched or found symbols at "C:\Users\danagostar\Downloads\DrMemory-Windows-2.3.0-1\DrMemory-Windows-2.3.0-1\logs\symbols\wkernel32.pdb\983A5BCBA20F455A3E11AA50FB3A3FD01\wkernel32.pdb"
Fetching symbols for "C:\WINDOWS\system32\gdi32.dll", attempt #0
Successfully fetched or found symbols at "C:\Users\danagostar\Downloads\DrMemory-Windows-2.3.0-1\DrMemory-Windows-2.3.0-1\logs\symbols\wgdi32.pdb\EC26B17219AF25A2531508809FB3C8821\wgdi32.pdb"
Fetching symbols for "C:\WINDOWS\system32\imm32.dll", attempt #0
Successfully fetched or found symbols at "C:\Users\danagostar\Downloads\DrMemory-Windows-2.3.0-1\DrMemory-Windows-2.3.0-1\logs\symbols\wimm32.pdb\AFB23A7345810B3301B1114EEC34E5F21\wimm32.pdb"
Fetching symbols for "C:\WINDOWS\system32\user32.dll", attempt #0
Successfully fetched or found symbols at "C:\Users\danagostar\Downloads\DrMemory-Windows-2.3.0-1\DrMemory-Windows-2.3.0-1\logs\symbols\wuser32.pdb\D8151310C41FA6924A249954568C13B21\wuser32.pdb"
Fetching symbols for "C:\WINDOWS\system32\win32u.dll", attempt #0
Successfully fetched or found symbols at "C:\Users\danagostar\Downloads\DrMemory-Windows-2.3.0-1\DrMemory-Windows-2.3.0-1\logs\symbols\wwin32u.pdb\C09DDFC96D57A1CF40F804DF931A3C0C1\wwin32u.pdb"
Searching for system calls in "C:\WINDOWS\system32\ntdll.dll"
Found 483 system calls (0 usercalls) in "C:\WINDOWS\system32\ntdll.dll"
Searching for system calls in "C:\WINDOWS\system32\kernelbase.dll"
Found 14 system calls (0 usercalls) in "C:\WINDOWS\system32\kernelbase.dll"
Searching for system calls in "C:\WINDOWS\system32\kernel32.dll"
Found 0 system calls (0 usercalls) in "C:\WINDOWS\system32\kernel32.dll"
Searching for system calls in "C:\WINDOWS\system32\gdi32.dll"
Found 0 system calls (0 usercalls) in "C:\WINDOWS\system32\gdi32.dll"
Searching for system calls in "C:\WINDOWS\system32\imm32.dll"
Found 0 system calls (0 usercalls) in "C:\WINDOWS\system32\imm32.dll"
Searching for system calls in "C:\WINDOWS\system32\user32.dll"
Found 93 system calls (92 usercalls) in "C:\WINDOWS\system32\user32.dll"
Searching for system calls in "C:\WINDOWS\system32\win32u.dll"
Found 1256 system calls (0 usercalls) in "C:\WINDOWS\system32\win32u.dll"
Writing to "C:\Users\danagostar\Downloads\DrMemory-Windows-2.3.0-1\DrMemory-Windows-2.3.0-1\drmemory\logs\symcache\syscalls_wow64.txt"
Successfully wrote "C:\Users\danagostar\Downloads\DrMemory-Windows-2.3.0-1\DrMemory-Windows-2.3.0-1\drmemory\logs\symcache\syscalls_wow64.txt"
Auto-generation succeeded. Re-launching the application.
<Using system call file C:\Users\danagostar\Downloads\DrMemory-Windows-2.3.0-1\DrMemory-Windows-2.3.0-1\drmemory\logs\symcache\syscalls_wow64.txt>
<drstrace log file is .\drstrace.calc.exe.16000.0000.log>
<Application C:\Users\danagostar\Downloads\DrMemory-Windows-2.3.0-1\DrMemory-Windows-2.3.0-1\bin64\calc.exe (16000). Dr. STrace internal crash at PC 0x6b0265e5. Please report this at http://drmemory.org/issues. Program aborted.
0xc0000005 0x00000000 0x6b0265e5 0x6b0265e5 0x00000001 0x6b0bac04
Base: 0x6af80000
Registers: eax=0x00000001 ebx=0x1baf1c40 ecx=0x00000001 edx=0x00000000
esi=0x00000000 edi=0x1baf1c40 esp=0x0420f348 ebp=0x0420f3e8
eflags=0x000
version 7.91.18298, custom build
-no_dynamic_options -logdir 'C:\Users\danagostar\Downloads\DrMemory-Windows-2.3.0-1\DrMemory-Windows-2.3.0-1\bin64' -client_lib 'C:\Users\danagostar\Downloads\DrMemory-Windows-2.3.0-1\DrMemory-Windows-2.3.0-1\bin\release\drstracelib.dll;0;-symcache_path `C:\Users\danagostar\Downloads\DrMemory-Windows-2.3.0-1\DrMemory-Win
0x0420f3e8 0x00000000>

[sltTn]

drstrace.calc.exe.16000.0000.log
finally, this result happened

[gonchik]

Hi!
I have met with issue on Windows Server 2019, (1809)