On 31.07.2017 19:51, Johnson Jones wrote:
On Saturday, 22 July 2017 at 12:54:17 UTC, Rainer Schuetze wrote:
On 18.06.2017 20:25, Mike B Johnson wrote:
[...]
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.
I installed a fresh VS2017 and the latest beta visual D and same issues.
As of today, was this suppose to be fixed?
It hasn't been released until now:
https://github.com/dlang/visuald/releases/tag/v0.45.0
