diff options
author | Rasmus Villemoes <rasmus.villemoes@prevas.dk> | 2018-09-12 16:06:36 +0200 |
---|---|---|
committer | Denys Vlasenko <vda.linux@googlemail.com> | 2018-10-31 11:13:55 +0100 |
commit | 571e525a141a2de87b9c2ced485745e96418d921 (patch) | |
tree | 0841c003d074777df7cb3a0fd7ece733b7bf9988 /testsuite/tar/tar-demands-at-least-one-ctx | |
parent | 93ef5dd640ef41edc72c80fa59c7cc9427b5945b (diff) | |
download | busybox-571e525a141a2de87b9c2ced485745e96418d921.tar.gz |
libbb: optionally honour libc provided SIGRTMIN/SIGRTMAX in get_signum()
When an application documents that it responds such and such to
SIGRTMIN+n, that almost always means with respect to the libc-provided
SIGRTMIN. Hence I disagree with the "more correct" in commit
7b276fc17594. In any case, this is rather unfortunate:
36
34
(the first shell is bash). We probably can't change default behaviour
after 7 years, but at least we can provide a config option.
We avoid a little code generation (repeated calls to
__libc_current_sigrtmin) by stashing SIGRTMIN/SIGRTMAX in local
variables, but it does cost ~50 bytes. The next patch serves as penance
for that.
Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
Diffstat (limited to 'testsuite/tar/tar-demands-at-least-one-ctx')
0 files changed, 0 insertions, 0 deletions