| commit | 6bc024e713fd35eb5fddbe16acd8dc92d27872a9 | |
| author | Laurent Vivier <laurent@vivier.eu> | |
| Wed, 12 Feb 2020 12:56:58 +0000 (12 13:56 +0100) | ||
| committer | Laurent Vivier <laurent@vivier.eu> | |
| Wed, 12 Feb 2020 17:56:41 +0000 (12 18:56 +0100) | ||
| tree | ec7229f3d63b2b4071d8d4ab12da477a62e9b38f | treesnapshot (tar.gz zip) |
| parent | 9fcff3a67f2be53de2d9b27c270ba2a4ecba8810 | commitdiff |
linux-user: fix use of SIGRTMIN
Some RT signals can be in use by glibc,
it's why SIGRTMIN (34) is generally greater than __SIGRTMIN (32).
So SIGRTMIN cannot be mapped to TARGET_SIGRTMIN.
Instead of swapping only SIGRTMIN and SIGRTMAX, map all the
range [TARGET_SIGRTMIN ... TARGET_SIGRTMAX - X] to
[__SIGRTMIN + X ... SIGRTMAX ]
(SIGRTMIN is __SIGRTMIN + X).
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
Reviewed-by: Taylor Simson <tsimpson@quicinc.com>
Tested-by: Taylor Simpson <tsimpson@quicinc.com>
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Message-Id: <20200212125658.644558-5-laurent@vivier.eu>
Some RT signals can be in use by glibc,
it's why SIGRTMIN (34) is generally greater than __SIGRTMIN (32).
So SIGRTMIN cannot be mapped to TARGET_SIGRTMIN.
Instead of swapping only SIGRTMIN and SIGRTMAX, map all the
range [TARGET_SIGRTMIN ... TARGET_SIGRTMAX - X] to
[__SIGRTMIN + X ... SIGRTMAX ]
(SIGRTMIN is __SIGRTMIN + X).
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
Reviewed-by: Taylor Simson <tsimpson@quicinc.com>
Tested-by: Taylor Simpson <tsimpson@quicinc.com>
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Message-Id: <20200212125658.644558-5-laurent@vivier.eu>
| linux-user/signal.c | diffblobblamehistory | |
| linux-user/trace-events | diffblobblamehistory |