April 10, 2013 Re: Sooo, umm, status of Optlink Issue #6144? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Walter Bright | 10.04.2013 2:20, Walter Bright пишет: > On 4/9/2013 2:41 PM, Denis Shelomovskij wrote: >> But I have to say I see the only one reason for it here. It is "Wow, >> that nasty >> person who used to insult everybody just did something useful. Lets >> say "Thanks" >> hoping he will like it and begin being useful". > > You've been doing valuable stuff all along. It's why we put up with you :-) > > I would, however, prefer that when you fire a broadside that you direct > it at me rather than others here. > >> So I'd like, if you don't mind, to redirect the "Thanks" to the >> (really time >> wasting and useful in a context of recent "shared library" talks and >> changes) >> fact I fixed TLS loading on Windows XP (yes, just finished what Rainer >> started) >> thus allowing languages like D to load/unload DLL-s dynamically. > > This is great news. Can you point me to the pull req on that? > No pulls, it isn't a part of druntime. It can be but only in the case executable is compiled. For D DLL it have to be loaded before the DLL and must not be unloaded until process termination. NG post: http://forum.dlang.org/thread/kf877d$iqd$1@digitalmars.com NG post notes: * replace `snn.dll` with `snn.lib` * according the injector, regressions are easily fought but Issue 9044 prevented it from being able to build -- Денис В. Шеломовский Denis V. Shelomovskij |
April 10, 2013 Re: Sooo, umm, status of Optlink Issue #6144? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Nick Sabalausky | 08.04.2013 23:33, Nick Sabalausky пишет: > Regarding the blocker "Unexpected OPTLINK Termination at EIP=00428DA3": > http://d.puremagic.com/issues/show_bug.cgi?id=6144 > > I'm hitting on that issue now too, and it's a royal PITA since I can't > even get stack traces, there's no obvious way to de-trigger the > problem and the problem is known to resist minimized test cases. > > So what's the current status of it (which I ask hoping the answer is > something like "a top priority being actively worked on")? > > More importantly, is there any info/files/etc I can provide to help > out, or is everything needed already known and merely awaiting a fix > from anyone who knows much more about optlink than I do? > Walter Bright properly fixed the issue. See http://d.puremagic.com/issues/show_bug.cgi?id=6144#c15 for the fix and fixed OPTLINK build. -- Денис В. Шеломовский Denis V. Shelomovskij |
April 10, 2013 Re: Sooo, umm, status of Optlink Issue #6144? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Denis Shelomovskij | On Wednesday, 10 April 2013 at 10:27:07 UTC, Denis Shelomovskij wrote: > Walter Bright properly fixed the issue. See http://d.puremagic.com/issues/show_bug.cgi?id=6144#c15 for the fix and fixed OPTLINK build. Hooray! I had the same problem in a recent project [1] and can confirm now the linker doesn't crash anymore. [1]: https://bitbucket.org/infognition/undup |
Copyright © 1999-2021 by the D Language Foundation