Are there any known remaining deadlock bugs in OPTLINK?

Walter Bright via Digitalmars-d digitalmars-d at puremagic.com
Sat May 27 01:57:28 PDT 2017


On 5/25/2017 7:16 AM, Vladimir Panteleev wrote:
> Here's three CI runs of the same commit on Windows:
> 
> https://ci.appveyor.com/project/CyberShadow/digger/build/1.0.108
> https://ci.appveyor.com/project/CyberShadow/digger/build/1.0.109
> https://ci.appveyor.com/project/CyberShadow/digger/build/1.0.110
> 
> The first two got stuck in a link.exe (OPTLINK) invocation and timed out.
> 
> - Does OPTLINK use threads or thread synchronization primitives?

Yes.

> - Is anyone aware of any threading/deadlock bugs in OPTLINK?
> - Any known workarounds? Like setting CPU affinity?

The CPU affinity is set in the Optlink executable, as it locks up without it.

> I've never experienced such hangs while I was still using Windows on my 
> development machine, though I think I did notice some hangs under Wine.
> 
> Digger makes sure to install OPTLINK 8.00.15 (latest at this time, AFAIK) from 
> http://downloads.dlang.org/other/.

8.00.17 is the latest.


More information about the Digitalmars-d mailing list