crash

[migurazi]

Dr. Memory version 2.3.0 Running ""D:\Works\2. Source\xxxxxxxxxx.exe"" Using system call file C:\Users\xxxx\AppData\Roaming\Dr. Memory\symcache\syscalls_x64.txt <Application D:\Works\2. Source\xxxxxxxxxx.exe (16364). Dr. Memory internal crash at PC 0x00007ff5f94fccd3. Please report this at http://drmemory.org/issues along with the results of running '-debug -dr_debug'. Program aborted. 0xc0000005 0x00000000 0x00007ff5f94fccd3 0x00007ff5f94fccd3 0x0000000000000000 0x0000000000000000 Base: 0x0000000071000000 Registers: eax=0x0000000000000000 ebx=0xffffffffffffffff ecx=0x000001b7750d01a4 edx=0x00000000000000fe esi=0x000001b7743bcce3 edi=0x0000000000000000 esp=0x0000008e0898bbe0 ebp=0x0000008e0898bce0 r8 =0x0000000000000000 r9 =0x0000000000000000 r10=0x0000000000000000 r11=0x000001b7d23a0000 r12=0x000000000001639d r13=0x0000008e0898c1f0 r14=0x000001b752ab6380 r15=0x000001b773791070 eflags=0x000004d000010256 2.3.0-1-(Feb 6 2020 06:07:09) WinVer=105;Rel=1909;Build=18363;Edition=Professional -no_dynamic_options -disasm_mask 8 -logdir 'C:\Users\xxxx\AppData\Roaming\Dr. Memory\dynamorio' -client_lib 'C:\Program Files (x86)\Dr. Memory\bin64\release\drmemorylib.dll;0;-visual_studio -logdir C:\Users\xxxx\AppData\Roaming\Dr. Memory -symcache_dir C:\Users\xxxx\AppData\Roaming\Dr. Memory\symcache -lib_blackli 0x0000008e0898bce0 0x0000000000000000>

[derekbruening]

There is not enough information here. You seem to have bypassed (there is a github bug where it doesn't show the template if you don't authenticate until the very last second) the bug filing template which asks for particular information. Pasting it here:

Describe the bug A clear and concise description of what the bug is.

If you just have a question, please use the users list https://groups.google.com/forum/#!forum/DrMemory-Users instead of this issue tracker, 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. If you are not sure it's a bug, please start by asking on the users list. If you have already asked on the users list and the consensus was to file a new issue, please include the URL to the discussion thread here.

To Reproduce Steps to reproduce the behavior:

1. Pointer to a minimized application (ideally the source code for it and instructions on which toolchain it was built with).
2. Precise command line for running the application.
3. Exact output or incorrect behavior.

Please also answer these questions drawn from https://github.com/DynamoRIO/drmemory/wiki/Debugging#narrowing-down-the-source-of-the-problem :

• Does the problem go away when running in light mode (pass -light to Dr. Memory)?
• Does the problem go away when running with the options -leaks_only -no_count_leaks -no_track_allocs?
• Does the problem go away when running under plain DynamoRIO? Do this by running dynamorio/bin32/drrun -- <application and args> or dynamorio/bin64/drrun -- <application and args> depending on the bitwidth of your applicaiton. (Ignore warnings about "incomplete installation".)
• What happens with the debug version of Dr. Memory and of its underlying engine DynamoRIO? Try this by passing -debug -dr_debug -pause_at_assert. Are any messages reported?

Expected behavior A clear and concise description of what you expected to happen.

Screenshots or Pasted Text If applicable, add screenshots to help explain your problem. For text, please cut and paste the text here, delimited by lines consisting of three backtics to render it verbatim, like this:

```
paste output here
```

Versions

• What version of Dr. Memory are you using?
• Does the latest build from https://github.com/DynamoRIO/drmemory/wiki/Latest-Build solve the problem?
• What operating system version are you running on? ("Windows 10" is not sufficient: give the release number.)
• Is your application 32-bit or 64-bit?

Additional context Add any other context about the problem here.