• Atila Neves (11/11) Feb 16 2017 This fails for me in a DLL:
• kinke (5/17) Feb 16 2017 If you suspect `new` of returning null, a GC issue seems likely.
• Atila Neves (4/26) Feb 16 2017 Whatever's default on Windows 32-bit. The thing is, all other

Atila Neves <atila.neves gmail.com> writes:

This fails for me in a DLL:

auto tid = spawn(&func);
assert(tid != Tid.init);

If I print out the tid, I find that its message box is null. This 
is odd, since according the code in std.concurrency there's 
nothing weird about how it gets a message box, it's just `auto 
spawnTid = Tid(new MessageBox);`. So... `new` is returning null???

The really weird thing is that a thread is spawned and func 
starts executing. I just can't send it any messages without 
crashing.

Atila

kinke <noone nowhere.com> writes:

On Thursday, 16 February 2017 at 12:07:40 UTC, Atila Neves wrote:
 This fails for me in a DLL:

 auto tid = spawn(&func);
 assert(tid != Tid.init);

 If I print out the tid, I find that its message box is null. 
 This is odd, since according the code in std.concurrency 
 there's nothing weird about how it gets a message box, it's 
 just `auto spawnTid = Tid(new MessageBox);`. So... `new` is 
 returning null???

 The really weird thing is that a thread is spawned and func 
 starts executing. I just can't send it any messages without 
 crashing.

 Atila

If you suspect `new` of returning null, a GC issue seems likely. 
Is your DLL linked statically against druntime, thus having its 
own GC? Or are you using a shared druntime (and thus GC) across 
multiple binaries?

Atila Neves <atila.neves gmail.com> writes:

On Thursday, 16 February 2017 at 15:14:25 UTC, kinke wrote:
 On Thursday, 16 February 2017 at 12:07:40 UTC, Atila Neves 
 wrote:
 This fails for me in a DLL:

 auto tid = spawn(&func);
 assert(tid != Tid.init);

 If I print out the tid, I find that its message box is null. 
 This is odd, since according the code in std.concurrency 
 there's nothing weird about how it gets a message box, it's 
 just `auto spawnTid = Tid(new MessageBox);`. So... `new` is 
 returning null???

 The really weird thing is that a thread is spawned and func 
 starts executing. I just can't send it any messages without 
 crashing.

 Atila

 If you suspect `new` of returning null, a GC issue seems 
 likely. Is your DLL linked statically against druntime, thus 
 having its own GC? Or are you using a shared druntime (and thus 
 GC) across multiple binaries?

Whatever's default on Windows 32-bit. The thing is, all other 
uses of GC allocations in the same DLL work as expected.

Atila