Visual D no bp's on x64

[Rainer Schuetze via Digitalmars-d-debugger]

On 18.06.2017 20:25, Mike B Johnson wrote:
>> I could produce an issue when starting the mago debugger for the first 
>> time after firing up VS2015: it showed an error, though, instead of 
>> not doing anything at all. Maybe it's a different effect of the same 
>> problem. I have added a work around that fixes it for me: 
>> https://ci.appveyor.com/project/rainers/visuald/build/job/5a92e21e7hxgty4b/artifacts 
>>
>>
>> BTW: the output window should show whether symbols for your 
>> application have been loaded. If not, you get the behavior that you 
>> reported.
> 
> Didn't work ;/
> 
> All I get on the output wndow is
> 
> "
> C:\Windows\System32\dbghelp.dll unloaded.
> The thread 0x1ea4 has exited with code -1 (0xffffffff).
> The thread 0x1390 has exited with code -1 (0xffffffff).
> The thread 0x1ac has exited with code -1 (0xffffffff).
> The program '[492] Async.exe' has exited with code -1 (0xffffffff).
> "

After installing VS2017 on a fresh Win10 install I could reproduce this 
issue: the mago debug engine failed to load the symbols when only VS2017 
is installed, because the COM-CLSID to load msdia140.dll changed. 
Switching to the VS debug engine worked, though.

Should be fixed in the next release.