[Issue 21066] Druntime SIGSEGV / SIGBUS unittest signal handler should emit the stack trace for all threads
d-bugmail at puremagic.com
d-bugmail at puremagic.com
Mon Jul 4 17:31:29 UTC 2022
https://issues.dlang.org/show_bug.cgi?id=21066
Andrej Mitrovic <andrej.mitrovich at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #3 from Andrej Mitrovic <andrej.mitrovich at 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.
--
More information about the Digitalmars-d-bugs
mailing list