New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Numeric values of signals are wrong (say +SIGUSR1) #6488
Comments
From @AlexDanielCode: Result: However, on my system SIGUSR1 is *not* 30 (it is 10). I guess rakudo should try harder to find proper values of the system it runs on. See this doc issue: Raku/doc#1474 |
From @AlexDanielWe now have a note in the docs about this. When fixed, change the docs accordingly (*maybe* saying that versions before X are known to have a bug). See IRC discussion: https://irclog.perlgeek.de/perl6/2017-09-01#i_15103501
|
From @AlexDanielThere's something regression-ish about it. Code: ¦79b8ab9d3f^: 10 ¦79b8ab9d3f: See (2017-06-02) rakudo/rakudo@79b8ab9 On 2017-09-01 15:39:42, alex.jakimenko@gmail.com wrote:
|
From @zoffixznetOn Fri, 13 Oct 2017 23:34:51 -0700, alex.jakimenko@gmail.com wrote:
Something fishy going on with the Signals enum. If that's fixed then the <Zoffix__> c: 79b8ab9d3f^,79b8ab9d3f,HEAD say SIGUSR1.Numeric; say SIGUSR1.value; say $*KERNEL.signal: SIGUSR1 |
The RT System itself - Status changed from 'new' to 'open' |
From @AlexDanielSomeone asked why this issue is ANNOYING, here's some clafirication. Basically, most of the stuff said said in linked comment applies here as well: https://rt-archive.perl.org/perl6/Ticket/Display.html?id=131003#txn-1496218 In other words, *some* signals have correct values and you don't notice the issue right away. Also, there's practically no workaround, unless you start hard-coding the values. I guess hard-coding can be counted as a workaround, except that it won't work on all systems. And this issue is very likely to be noticed by anybody using SIGUSR1. I think that's enough to justify the tag. FWIW, I've also made a note about this issue in the docs, to prevent people from wasting their time on a known issue: https://docs.perl6.org/type/Supply#sub_signal On 2017-09-01 03:33:34, alex.jakimenko@gmail.com wrote:
|
From @zoffixznetOn Sat, 14 Oct 2017 08:29:50 -0700, cpan@zoffix.com wrote:
There's also a failing spectest on Windows that expects both of these to give same value (on and Linux, they do): C:\rakudo>perl6 -e "$*KERNEL.signal('SIGHUP').say" C:\rakudo>perl6 -e "$*KERNEL.signal(SIGHUP).say" |
From @AlexDanielFurther discussion on rakudo/rakudo#1588 On 2017-10-18 03:46:20, cpan@zoffix.com wrote:
|
@AlexDaniel - Status changed from 'open' to 'rejected' |
Migrated from rt.perl.org#132012 (status was 'rejected')
Searchable as RT132012$
The text was updated successfully, but these errors were encountered: