-
Notifications
You must be signed in to change notification settings - Fork 577
keys %SIG contains 'SIGUNUSED' #16330
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
Comments
From @jimavThis is a bug report for perl from jim.avera@gmail.com, $ perl -we 'local @SIG{ keys %SIG };' There is an easy work-around, namely localizing only the specific However something isn't right if there is a key in %SIG which Flags: Site configuration information for perl 5.26.0: Configured by Debian Project at Fri Sep 15 16:13:42 UTC 2017. Summary of my perl5 (revision 5 version 26 subversion 0) configuration: Locally applied patches: @INC for perl 5.26.0: Environment for perl 5.26.0: |
From @tonycozOn Wed, Dec 20, 2017 at 01:55:45PM -0800, via RT wrote:
Do you see this only with the Debian build of perl, or with a build I'm wondering if this was introduced by the patch discussed in: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875927 The original issue was also discussed at https://rt-archive.perl.org/perl5/Ticket/Display.html?id=132105 Tony |
The RT System itself - Status changed from 'new' to 'open' |
From @ntyniOn Thu, Dec 21, 2017 at 09:18:20AM +1100, Tony Cook wrote:
It's clearly related, but the report is about Ubuntu's perl I think Ubuntu applied an earlier and different fix as a result of https://bugs.launchpad.net/ubuntu/+source/libanyevent-perl/+bug/1717367 but I can't seem to find a link the actual patch easily... |
From @jimavThe perl comes with Ubuntu 17.10, which I am guessing is the same as I have not tried compiling Perl from source. On Dec 20, 2017 2:18 PM, "Tony Cook via RT" <perlbug-followup@perl.org>
|
From @ntyniOn Sun, Dec 24, 2017 at 09:13:11PM -0800, Jim Avera wrote:
No, they are not the same. I managed to find a link for the relevant Ubuntu change: http://deriv.debian.net/patches/p/perl/Debian_perl_5.26.0-8_Ubuntu_perl_5.26.0-8ubuntu1.debian.patch while the change that went into Debian later is at https://anonscm.debian.org/cgit/perl/perl.git/commit/?id=c476030a3d41e535e5f5500fe58df21ffd87c242 Both attempt to re-add SIGUNUSED for binary compatibility when building on However, Ubuntu's adding zero to SIG_NUM looks wrong and the probable So I think this can only be fixed in Ubuntu, and presumably somebody Hope this helps, |
From @jimavOn Tue, 26 Dec 2017 11:17:27 -0800, ntyni@debian.org wrote:
Done. |
@iabyn - Status changed from 'open' to 'rejected' |
Migrated from rt.perl.org#132631 (status was 'rejected')
Searchable as RT132631$
The text was updated successfully, but these errors were encountered: