On Tue, Feb 4, 2020 at 3:55 AM Laurent Vivier wrote:
> We should add signal 63 here, but it's becoming not very clean.
https://golang.org/issue/33746 has some discussion of the issue. The
Go maintainers wanted to clean this up rather than just adding 63. The
patch is on ice right now because it w
Le 04/02/2020 à 01:03, Josh Kunz a écrit :
> On Sat, Feb 1, 2020 at 4:27 AM Laurent Vivier wrote:
>> This has been tested with Go (golang 1.10.1 linux/arm64, bionic) on x86_64
>> fedora 31. We can avoid the failure in this case allowing the unsupported
>> signals when we don't provide the "act" pa
On Sat, Feb 1, 2020 at 4:27 AM Laurent Vivier wrote:
> This has been tested with Go (golang 1.10.1 linux/arm64, bionic) on x86_64
> fedora 31. We can avoid the failure in this case allowing the unsupported
> signals when we don't provide the "act" parameters to sigaction, only the
> "oldact" one.
l@nongnu.org
> Cc: Josh Kunz ; milos.stojano...@rt-rk.com; Matus Kysel
> ; Aleksandar Markovic rk.com>; Marlies Ruck ; Laurent Vivier
> ; Peter Maydell ; Taylor
> Simpson ; Riku Voipio
> Subject: [PATCH 0/4] linux-user: fix use of SIGRTMIN
>
> This series fixes the problem of
This series fixes the problem of the first real-time signals already
in use by the glibc that are not available for the target glibc.
Instead of reverting the first and last real-time signals we rely on
the value provided by the glibc (SIGRTMIN) to know the first available
signal and we map all th
