VisualD 64bit linker error

[Rainer Schuetze via Digitalmars-d-ide]

On 23.11.2014 00:02, sdvcn wrote:
> On Saturday, 22 November 2014 at 10:17:59 UTC, Rainer Schuetze wrote:
>>
>>
>> On 20.11.2014 09:27, sdvcn wrote:
>>> On Friday, 14 November 2014 at 17:14:25 UTC, Rainer Schuetze wrote:
>>>>
>>>>
>>>> On 14.11.2014 16:33, Charles wrote:
>>>>> On Friday, 14 November 2014 at 11:13:32 UTC, Rainer Schuetze
>>>>> wrote:
>>>>>
>>>>>> As a workaround, please rename the configuration to something that
>>>>>> doesn't contain spaces.
>>>>>
>>>>> I thought that's what the issue was; however, I'm not sure where
>>>>> to update the config at.
>>>>
>>>> Go to the configuration manager, select the project configuration and
>>>> click "Edit" in the drop-down list. The following dialog allows
>>>> renaming...
>>>
>>> 日志名称:          Application
>>> 来源:            Application Error
>>> 日期:            2014/11/20 15:44:13
>>> 事件 ID:         1000
>>> 任务类别:          (100)
>>> 级别:            错误
>>> 关键字:           经典
>>> 用户:            暂缺
>>> 计算机:           WIN-6RRLID41QMM
>>> 描述:
>>> 错误应用程序名称: link.exe，版本: 12.0.30324.0，时间戳: 0x532f655e
>>> 错误模块名称: filemonitor.dll，版本: 0.0.0.0，时间戳: 0x00000000
>>> 异常代码: 0xc0000005
>>> 错误偏移量: 0x0000309b
>>> 错误进程 ID: 0xd70
>>> 错误应用程序启动时间: 0x01d00495ab86ed5a
>>> 错误应用程序路径: C:\Program Files (x86)\Microsoft Visual Studio
>>> 12.0\VC\bin\link.exe
>>> 错误模块路径: C:\Program Files (x86)\VisualD\filemonitor.dll
>>> 报告 ID: 04e0d41e-7089-11e4-ae24-00e066349802
>>>
>>>
>>> filemonitor.dll error
>>>
>>> https://github.com/D-Programming-Language/visuald/raw/master/tools/filemonitor.d
>>>
>>>
>>> Compile replacement
>>>
>>
>> I can't really decipher this but I guess it's some kind of crash report.
>>
>> There have been some recent fixes to the file monitor. Have you tried
>> one of the latest betas:
>> https://github.com/D-Programming-Language/visuald/releases ?
>
> (Visual D v0.3.40 beta 2) This package filemonitor.dll file is wrong.

I'm not sure what's wrong with it. It is known to be reported by some 
Anti-Virus programs because it is injected into the linker process, 
though. Is this the issue here?