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
Bleadperl 8165fae breaks Sys::AlarmCall #11260
Comments
From @cpansproutSee https://rt.cpan.org/Ticket/Display.html?id=67239 and: commit 8165fae Move PERL_ASYNC_CHECK() from POPBLOCK() to the kill case of Perl_apply(). Flags: Site configuration information for perl 5.14.0: Configured by sprout at Sun Apr 3 16:29:04 PDT 2011. Summary of my perl5 (revision 5 version 14 subversion 0) configuration: Locally applied patches: @INC for perl 5.14.0: Environment for perl 5.14.0: |
From @cpansproutCan this be made a blocker? |
From @obraOn Sun 17.Apr'11 at 17:18:31 -0700, Father Chrysostomos wrote:
It now blocks. Thanks. |
The RT System itself - Status changed from 'new' to 'open' |
From @iabynOn Mon, Apr 18, 2011 at 12:11:07PM +1000, Jesse Vincent wrote:
Now fixed: commit 011c381 dispatch signals when leaving an eval -- |
@iabyn - Status changed from 'open' to 'resolved' |
From @nwc10On Tue, Apr 19, 2011 at 02:34:09PM +0100, Dave Mitchell wrote:
Thanks. Your timing is perfect. I'd got the test case down to the same size as I'm glad that the fix is clean and simple, as I was concerned that it was (A: Because if a PERL_ASYNC_CHECK() is missing from somewhere it should be, Nicholas Clark |
Migrated from rt.perl.org#88774 (status was 'resolved')
Searchable as RT88774$
The text was updated successfully, but these errors were encountered: