new(malloc) locks everything in multithreading

[Kapps via Digitalmars-d-learn]

On Friday, 24 October 2014 at 10:49:42 UTC, tcak wrote:
> On Friday, 24 October 2014 at 10:46:57 UTC, tcak wrote:
>> On Friday, 24 October 2014 at 10:29:10 UTC, Kagamin wrote:
>>> Looks like your IDE filters too much. Can you configure it to 
>>> filter less and show address locations?
>>
>> This is what I have found:
>>
>> Main Thread
>> http://i.imgur.com/6ElZ3Fm.png
>>
>> Second Thread (TestThread)
>> http://i.imgur.com/w4y5gYB.png
>
> BTW, instead of using Monodevelop with Mono-D, I used same code 
> on a text
> file, and compiled with "dmd test.d", then run with "./test", 
> then everything
> works fine. When I run it with "gdb ./test", then I can see 
> those errors again.

Not sure if this is the same issue, but by default gdb breaks on 
signals that the GC uses, which would explain why it's breaking 
in gdb but not normally.

What happens if you try:
handle SIGUSR1 noprint nostop
handle SIGUSR2 noprint nostop

In GDB before starting execution of the program?