DynamoRIO / DynamoRIO/drmemory
Crash when trying to debug application from Visual Studio 19
- Dominant language
- C
- Stars
- 2.7k
- Forks
- 290
- PR merge metrics
- No merged PRs in 30d
Description
I tried to run Dr. Memory, 64-bit exe, on my application from within Visual Studio 2019 when I got that Dr. Memory internal crash. The thing is: I'm getting very strange crashes in the application I want to debug, in the context of freeing memory/unloading dlls, so I thought maybe there's some mem corruption I can analyze with Dr. Memory. But the strange thing is that this only happens in my Virtual Windows 10 (10.0.19044 Build 19044) machine, not in the virtual machine of a colleague, not on the native Windows installation of another colleague. And now Dr. Memory crashes with some strange output:
```
Dr. Memory version 2.5.0
Running "D:\eclipseWS\something\something_head_exe\exe\Debug\something.exe x/input.inp"
Using system call file D:\programme\DrMemory\drmemory\logs\symcache\syscalls_x64.txt
Dr. Memory version 2.5.0
Running "D:\eclipseWS\something\something_head_exe\exe\Debug\something.exe x/input.inp"
Using system call file D:\programme\DrMemory\drmemory\logs\symcache\syscalls_x64.txt
ASSERT FAILURE (thread 15512): D:\a\drmemory\drmemory\drmemory\syscall_windows.c:151: opc_is_in_syscall_wrapper(opc) (unknown system call sequence)
```
Can you make sense of these messages? Is there something wrong with my system?
Contributor guide
Assessment
This issue has not been assessed yet.