[Issue 15939] GC.collect causes deadlock in multi-threaded environment
via Digitalmars-d-bugs
digitalmars-d-bugs at puremagic.com
Mon May 9 12:32:04 PDT 2016
https://issues.dlang.org/show_bug.cgi?id=15939
--- Comment #12 from Aleksei Preobrazhenskii <apreobrazhensky at gmail.com> ---
(In reply to Martin Nowak from comment #11)
> Did you have gdb attached while the signal was send? That sometime causes
> issues w/ signal delivery.
No, I didn't. I attached gdb to investigate deadlock which already happened at
that point.
> Are there any other reasons for switching to real-time signals?
I read that traditional signals are internally mapped to real-time signals. If
that's true I see no reason to stick with inferior emulated entity with weaker
guarantees.
> Which real-time signals are usually not used for other purposes?
Basically all real-time signals from range SIGRTMIN .. SIGRTMAX are intended
for custom use (SIGRTMIN might vary from platform to platform though, because
of things like NPTL and LinuxThreads).
--
More information about the Digitalmars-d-bugs
mailing list