https://issues.dlang.org/show_bug.cgi?id=21066

FeepingCreature <default_357-line@yahoo.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |default_357-line@yahoo.de

--- Comment #1 from FeepingCreature <default_357-line@yahoo.de> ---
SIGSEGV will only be delivered to the thread that caused the segfault.

As per 'man 7 signal':

> A signal may be process-directed or thread-directed. [...] A thread-directed signal is one that is targeted at a specific thread. A signal may be thread-directed because it was generated as a consequence of executing a specific machine-language instruction that triggered a hardware exception (e.g., SIGSEGV for an invalid memory access, or SIGFPE for a math error)

--

https://issues.dlang.org/show_bug.cgi?id=21066

--- Comment #2 from FeepingCreature <default_357-line@yahoo.de> ---
Readable version:

> A signal may be process-directed or thread-directed. [...]
> A thread-directed signal is one that is targeted at a specific thread. A signal may be
> thread-directed because it was generated as a consequence of executing a specific
> A machine-language instruction that triggered a hardware exception (e.g., SIGSEGV for
> an invalid memory access, or SIGFPE for a math error)

--

https://issues.dlang.org/show_bug.cgi?id=21066

Andrej Mitrovic <andrej.mitrovich@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #3 from Andrej Mitrovic <andrej.mitrovich@gmail.com> ---
(In reply to FeepingCreature from comment #2)
> Readable version:
> 
> > A signal may be process-directed or thread-directed. [...]
> > A thread-directed signal is one that is targeted at a specific thread. A signal may be
> > thread-directed because it was generated as a consequence of executing a specific
> > A machine-language instruction that triggered a hardware exception (e.g., SIGSEGV for
> > an invalid memory access, or SIGFPE for a math error)

Thanks. This might have been just a problem on MacOS. I don't have a MacOS machine to test this on anymore, and I'm not sure whether this problem occurred on other OSes.

> I have a working prototype for MacOS, but not for Posix / Windows / other platforms yet.

This work has been lost, unfortunately.

--