Thread overview
LDC mspdb140 error x64
Jun 08
kinke
June 08
LINK : fatal error LNK1171: unable to load mspdb140.dll (error code: 193)
Error: `VS\VC\Tools\MSVC\14.10.25017\bin\HostX86\x64\link.exe` failed with status: 1171

I'm pretty sure that it is using the x64 mspdb140.dll because procmon says it is

VS\VC\Tools\MSVC\14.10.25017\bin\HostX86\x64\mspdb140.dll

But maybe this isn't the correct one?

It seems to be looking in a bunch of dir's, including

ldc2\bin\mspdb140.dll

and the windows kit's, sdk, and VC dir, it finds them but I guess they are all x86.

It looks at

Windows Kits\8.1\bin\x64\mspdb140.dll

and just about every dir in the %path%... it finds many versions(x86 and x64) but never is satisfied.

and the dll is there but it doesn't use it.


Why does it need the pdb anyways? I thought that was for debugging?

June 08
On Thursday, 8 June 2017 at 02:18:16 UTC, Mike B Johnson wrote:
> LINK : fatal error LNK1171: unable to load mspdb140.dll (error code: 193)
> Error: `VS\VC\Tools\MSVC\14.10.25017\bin\HostX86\x64\link.exe` failed with status: 1171
>
> I'm pretty sure that it is using the x64 mspdb140.dll because procmon says it is
>
> VS\VC\Tools\MSVC\14.10.25017\bin\HostX86\x64\mspdb140.dll
>
> But maybe this isn't the correct one?
>
> It seems to be looking in a bunch of dir's, including
>
> ldc2\bin\mspdb140.dll
>
> and the windows kit's, sdk, and VC dir, it finds them but I guess they are all x86.
>
> It looks at
>
> Windows Kits\8.1\bin\x64\mspdb140.dll
>
> and just about every dir in the %path%... it finds many versions(x86 and x64) but never is satisfied.
>
> and the dll is there but it doesn't use it.
>
>
> Why does it need the pdb anyways? I thought that was for debugging?

The problem is that it seems to need the x86 version even when compiling for x64. When using x64, the paths are switched to x64 dlls and hence it fails to load it. I stuck the x86 dll in some path that it was looking in and it worked, but didn't work when I stuck the x64 dll in the same location overwriting the x86 version.


June 08
That's a VisualD issue, see https://issues.dlang.org/show_bug.cgi?id=17384.