Yet another Dr. Memory Internal Crash

**Describe the bug**

Dr. Memory (latest version) reproducible fails with an **_Internal Crash_** when testing my program!

```
Dr. Memory internal crash at PC 0x645a65e5. Please report this at... Program aborted.
```

For details please see the screenshot below!

**To Reproduce**

1. Please use files from [**DrM-InternalCrash.2020-07-29.zip**](https://github.com/DynamoRIO/drmemory/files/4995582/DrM-InternalCrash.2020-07-29.zip) to reproduce!
2. Run `"drmemory.exe" -- "my_program.exe" "ttttcattct" "quux" "input-3.txt" "output-3a.txt"`
3. Wait a little
4. See the crash dialog pop up (as shown in screenshot below)

**Please also answer these questions:**
- Does the problem go away when running in light mode (pass `-light` to Dr. Memory)?
***nope***
- Does the problem go away when running with the options `-leaks_only -no_count_leaks -no_track_allocs`?
***nope***
- Does the problem go away when running under plain DynamoRIO?
***yes!*** (seemed to finish normally)
- What happens with the debug version of Dr. Memory and of its underlying engine DynamoRIO?
***doesn't even start***
As soon as option `-dr_debug` is added to the invocation, Dr. Memory will crash right away with:
`~~Dr.M~~ WARNING: application exited with abnormal code 0xc0000005`

**Expected behavior**

Dr. Memory shouldn't crash with an internal error while testing my App.

**Screenshots or Pasted Text**


**Versions**

- What version of Dr. Memory are you using?
***2.3.0-1***
- Does the latest build solve the problem?
***nope***
But there is a new error message that I didn't see before:
`~~Dr.M~~ ERROR: Failed to find "main" for limiting memory dump`
- What operating system version are you running on?
***Windows 10 v2004 (x64)***
- Is your application 32-bit or 64-bit?
***32-Bit***
(also tried a 64-Bit compile, but same issue)