DynamoRIO / DynamoRIO/drmemory

Dr. Memory internal crash

Open
#2,302 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
2.7k
Forks
290
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**

Internal crash at PC `0x70766ca5`, `0x70fb6ca5` and `0x70b56ca5` (depending on flags passed)

Here is a complete command line and log file dump of all relevant Dr. Memory invocations: **[DrMemory_Internal_Crash_Logs.zip](https://github.com/DynamoRIO/drmemory/files/4836787/DrMemory_Internal_Crash_Logs.zip)**

Please also answer these questions:
- Does the problem go away when running in light mode (pass `-light` to Dr. Memory)?
**No (see zip file for exact logs)**
- Does the problem go away when running with the options `-leaks_only -no_count_leaks -no_track_allocs`?
**No (see zip file for exact logs)**
- Does the problem go away when running under plain DynamoRIO?
**Yes (see zip file for exact logs)**
- 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?
**See zip file for exact logs**

**Versions**
- What version of Dr. Memory are you using?
**2.3.18352**
- Does the latest build from
https://github.com/DynamoRIO/drmemory/wiki/Latest-Build solve the problem?
**No**
- What operating system version are you running on?
**Windows 10;WinVer=105;Rel=1909;Build=18363;Edition=EnterpriseN**
- Is your application 32-bit or 64-bit?
**32 bit
Compiled with `g++ (i686-posix-dwarf-rev0, Built by MinGW-W64 project) 8.1.0`
Using Qt framework `4.8.7`**

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.