Dr. Memory internal crash at PC 0x7383a079 , PC 0x0209a60a

Just wanted to check my (32bit) program for memory leaks ( running inside WOW64-Subsystem off Win8.1):

Calling Dr.Memory and my Programm in "server-mode" doesnt'crash:

```

BEGIN one line
start cmd /k P:\tools\DrMemory-Windows-1.8.1-RC1\bin\drmemory.exe -- %CD%\Socket2NamedPipe.exe -serverproxy pipenameR 979 cmd /k P:\tools\DrMemory-Windows-1.8.1-RC1\bin\drmemory.exe -- %CD%\Socket2NamedPipe.exe -server -L 979
END one line

```

Calling Dr.Memory and my Programm in "client-mode" crashs:

```

BEGIN one line
start cmd /k P:\tools\DrMemory-Windows-1.8.1-RC1\bin\drmemory.exe -- %CD%\Socket2NamedPipe.exe -clientproxy 127.0.0.1 pipenameR 978 cmd /k P:\tools\DrMemory-Windows-1.8.1-RC1\bin\drmemory.exe -- %CD%\Socket2NamedPipe.exe -client 127.0.0.1 978
END one line

```

Dr Memory crashes with this Message:

```

Dr. Memory internal crash at PC 0x7383a079.
Please report this at http://drmemory.org/issues.
Program aborted.
0xc0000005 0x0000000 0x7383a079 0x7383a079 0x0000000 0x006d0036
Base: 0x727e0000
Registers: eax=0x192de88c ebx=0x192de9b4
ecx=0x006d0032 edx=0xffffffff
esi=0x192de8c0 edi=0x00006d24
esp=0x192de85c ebp=0x006d0032
eflags=0x000
version 5.0.16470, custom build
-no_dynamic_options -disasm_mask 8 -logdir
'P:\tools\DrMemory-Windows-1.8.1-RC1\drmemory\logs\dynamorio'
-client_lib 'P:\tools\DrMemory-Windows-1.8.1-RC1\bin\release\drmemorylib.dll;0;
-logdir `P:\tools\DrMemory-Windows-1.8.1-RC1\drmemory\logs`
-symcache_dir `P:\tools\DrMemory-Windows-1.8.1-RC1\drmemory\logs\symcache`
-lib_blacklist C:\Windows*.d?? -resfile 2488' -code_api -probe
P:\tools\DrMemory-Windows-1.8.1-RC1\bin\release\drmemorylib.dll=0x73800000
P:\tools\DrMemory-Windows-1.8.1-RC1\bin\release/dbghelp.dll=0x72400000
c:\Windows/system32/msvcrt.dll=0x01e10000
c:\Windows/system32/kernel32.dll=0x01ee0000
c:\Windows/system32/KERNELBASE.dll=0x02020000

```

If I start MrMemory with the -light option, then I can see on console:

```

~~Dr.M~~
~~Dr.M~~ Error #1: UNADDRESSABLE ACCESS beyond heap bounds: writing 0x0288d4ed-0
x0288d4ee 1 byte(s)

```

perhaps this is a problem in my program?
perhaps my program runs without DrMemory just accidental?

If I replace the -light option with these options "-leaks_only -no_count_leaks -no_track_allocs"
than my program starts but its child process doesn't get started

Okay what I can get with -debug -dr_debug -pause_at_assert

```

~~Dr.M~~ Dr. Memory version 1.8.1
~~Dr.M~~ Running "P:\SocketANDNamedPipe\Socket2NamedPipe\Debug_SBCS\Socket2Named
Pipe.exe -clientproxy 127.0.0.1 pipenameR 978 cmd /k P:\tools\DrMemory-Windows-1
.8.1-RC1\bin\drmemory.exe -debug -dr_debug -pause_at_assert -- P:\SocketANDNamed
Pipe\Socket2NamedPipe\Debug_SBCS\Socket2NamedPipe.exe -client 127.0.0.1 978"
Called with parameters:

table_flags)) != 0) && table->capacity <= 513)) && "hash table high average coll
ision length" in file d:\drmemory_package\dynamorio\core\hashtablex.h line 1845
version 5.0.16470, custom build
-no_dynamic_options -logdir 'P:\tools\DrMemory-Windows-1.8.1-RC1\drmemory\logs\d
ynamorio' -client_lib 'P:\tools\DrMemory-Windows-1.8.1-RC1\bin\debug\drmemorylib
.dll;0;`-pause_at_assert` -logdir `P:\tools\DrMemory-Windows-1.8.1-RC1\drmemory\
logs` -symcache_dir `P:\tools\DrMemory-Windows-1.8.1-RC1\drmemory\logs\symcache`
-lib_blacklist C:\Windows*.d?? -resfile 4912 ' -code_api -pro
0x1fede88c 0x69640e2a
0x1fede95c 0x69646bc7
0x1fedea74 0x69646160
0x1fedeb10 0x69645760
0x1fedebac 0x6964364d
0x1feded60 0x696bac74
0x1fedee0c 0x696ba85f
0x1fedef18 0x696b6784
0x1fedeff4 0x1fea221c
0x0028ff08 0x004010fd
0x0028ff94 0x775db5af
0x0028ffdc 0x775db57a
0x0028ffec 0x00000000
P:\tools\DrMemory-Windows-1.8.1-RC1\bin\debug\drmemorylib.dll=0x01ec0000
P:\tools\DrMemory-Windows-1.8.1-RC1\bin\debug/dbghelp.dll=0x69490000
C:\Windows/system32/msvcrt.dll=0x02540000
C:\Windows/system32/kernel32.dll=0x02610000
C:\Windows/system32/KERNELBASE.dll=0x02750000>
"cmd" /k P:\tools\DrMemory-Windows-1.8.1-RC1\bin\drmemory.exe -debug -dr_debug -
pause_at_assert -- P:\SocketANDNamedPipe\Socket2NamedPipe\Debug_SBCS\Socket2Name
dPipe.exe -client 127.0.0.1 978

```

So which Application changes the protection of system memory ?
And a Dr.Memory Crash-info pops up:

```

Dr. Memory internal crash at PC 0x0209a60a
Please report this at http://drmemory.org/issues.
Program aborted.
0xc0000005 0x0000000 0x0209a60a 0x0209a60a 0x0000000 0x006d0036
Base: 0x695b0000
Registers: eax=0x006d0032 ebx=0x00000000
ecx=0x00000003 edx=0x1fedcec8
esi=0x002b013 edi=0x00000002
esp=0x1fedcaa4 ebp=0x1fedcb08
eflags=0x000
version 5.0.16470, custom build
-no_dynamic_options -disasm_mask 8 -logdir
'P:\tools\DrMemory-Windows-1.8.1-RC1\drmemory\logs\dynamorio'
-client_lib 'P:\tools\DrMemory-Windows-1.8.1-RC1\bin\release\drmemorylib.dll;0;
-logdir `P:\tools\DrMemory-Windows-1.8.1-RC1\drmemory\logs`
-symcache_dir `P:\tools\DrMemory-Windows-1.8.1-RC1\drmemory\logs\symcache`
-lib_blacklist C:\Windows*.d?? -resfile 4912' -code_api -pro
0x1fedcb08 0x020e473
0x1fedcf74 0x020dcf97
```

Except of using Dr.Memory with my Socket2NamedPipe program I hadn't problems in the past with your cool Dr.Memory. Very nice program. Thanks for that.

So I think the crash of Dr.Memory is caused by my program...

Best regards,
Robert