Crash in target process jumping into invalid memory

[baldurk]

For reasons currently unknown, sometimes using CreateToolhelp32Snapshot to find the renderdoc dll in the target process can fail, leading to jumping into 0x0+RENDERDOC_SetLogFile instead of renderdoc.dll+RENDERDOC_SetLogFile.

I've put a change in that will be included in v0.19 that includes better logging, a speculative fix and slightly more graceful handling of this happening.

[baldurk]

Figured this out, the module list from the snapshot can sometimes return renderdoc as RENDERDOC.DLL even if nothing refers to it as upper case. I'm sure there's a good reason for it, but since I didn't need a case sensitive comparison while looking for the module I made it case insensitive.