From: Eric Wong <normalperson@...>
Date: 2018-08-22T05:34:41+00:00
Subject: [ruby-core:88604] Re: [Ruby trunk Feature#15017] Provide extended information about Signal

> Feature #15017: Provide extended information about Signal
> https://bugs.ruby-lang.org/issues/15017#change-73659

Implementation would be tricky, since we defer signals to run
Ruby code.  (Deferring allows us to use malloc and other
non-async-safe C stdlib functions).

To implement, we'd have to reject [Misc #15011] (eventfd)[1] and
write "struct siginfo" to the pipe.

Or, write a async-signal-safe bump allocator...


[1] Too many full-sized pipes cause resource problems requiring ugly
    workarounds like r64478.

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>