Internal crash when debugging Pidgin (Windows 1.9.0-RC1)

```
---------------------------
Dr. Memory Notice: C:\Program Files (x86)\Pidgin\pidgin.exe(10580)
---------------------------
Application C:\Program Files (x86)\Pidgin\pidgin.exe (10580). Dr. Memory internal crash at PC 0x73861b9f. Please report this at http://drmemory.org/issues. Program aborted.
0xc0000005 0x00000000 0x73861b9f 0x73861b9f 0x00000000 0x0464a20c
Base: 0x70060000
Registers: eax=0x0464a211 ebx=0x28fc5508 ecx=0x00000000 edx=0xffffffff
esi=0x28f895fc edi=0x00000000 esp=0x2564e6cc ebp=0x0464a200
eflags=0x000
1.9.0-0-(Aug 28 2015 22:56:18) win100
-no_dynamic_options -disasm_mask 8 -logdir 'C:\Users\Eion Robb\AppData\Roaming\Dr. Memory\dynamorio' -client_lib 'C:\Program Files (x86)\Dr. Memory\bin\release\drmemorylib.dll;0;-logdir `C:\Users\Eion Robb\AppData\Roaming\Dr. Memory` -symcache_dir `C:\Users\Eion Robb\AppData\Roaming\Dr. Memory\symcache` -lib_blacklist `C
C:\Program Files (x86)\Dr. Memory\bin\release\drmemorylib.dll=0x73800000
C:\Program Files (x86)\Dr. Memory\bin\release/dbghelp.dll=0x02530000
C:\WINDOWS/system32/msvcrt.dll=0x00d10000
C:\WINDOWS/system32/kernel32.dll=0x02650000
C:\WINDOWS/system32/KERNELBASE.dll=0x02740000
```

> What steps will reproduce the problem?
1. Install a plugin compiled without ggdb, eg the Facebook Pidgin plugin, eg https://github.com/jgeboski/purple-facebook/releases/tag/565fbae05259
2. path\to\drmemory.exe -- path\to\pidgin.exe --debug
3. Last debug message will show a plugin has crashed drmemory, eg:

```
(14:11:24) plugins: probing C:\Program Files (x86)\Pidgin\plugins\libfacebook (8).dll
What is the expected output? What do you see instead?

Hoping that it will skip over that particular plugin and continue, rather than crash

> What version of the product are you using? On what operating system?

DrMemory 1.9.0-RC1 on Windows 10

> Does the problem go away when running in light mode (pass "-light" to Dr.
> Memory)? What about when running with the options "-leaks_only -no_count_leaks -no_track_allocs"?

"-light" does work mostly. It'll output

```
~~4108~~ WARNING: application is missing line number information.
~~4108~~ Re-compile with the -ggdb flag to include DWARF2 line numbers.
```

for the first plugin that isn't compiled with gdb, but it will still crash upon the next plugin without it comes across
Running with "-leaks_only -no_count_leaks -no_track_allocs" does not work, same crash
Also crashes with "-no_count_leaks" and "-leaks_only -no_count_leaks" (as per narrowing down the source

> Does the problem go away when using the most recent build from http://build.chromium.org/p/client.drmemory/builds/?

Unsure, will try later

> Try the debug version of Dr. Memory and of its underlying engine DynamoRIO by passing "-debug -dr_debug -pause_at_assert" to drmemory.exe. Are any
> messages reported?

Unsure, will try later

> Please provide any additional information below. Please also see the "Narrowing Down the Source of the Problem" section of https://github.com/DynamoRIO/drmemory/wiki/Debugging.

I imagine it's something to do with handling one block of non-ggdb compiled code, but not mixed dll's, some with and some without? Wild guess though :)