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
return out of first {body} #7225
Comments
From @lizmatCreated by @lizmatin 5.8.0, the following neatly returns an error message. -bash-2.05b$ perl5.8.0 -MList::Util=first -e 'first {return 1} (1)' in 5.8.1 and higher (including 5.8.4-RC1 and 5.9.0) gives a segfault: $ valgrind perl5.8.3 -MList::Util=first -e 'first {return 1} (1)' Perl Info
|
From @andk
Blame analysis: ----Program---- ----Output of .../pDGfVX1/perl-5.8.0@18075/bin/perl---- ----EOF ($?='65280')---- ----EOF ($?='11')---- Change 18076 by gbarr@monty on 2002/11/03 10:11:18 Update to Scalar-List-Utils 1.08 -- |
The RT System itself - Status changed from 'new' to 'open' |
From @iabynOn Sun, Apr 11, 2004 at 09:44:20AM +0200, Andreas J Koenig wrote:
Well, the direct segfault happens because the return pops a SUB context Not sure of the best way of fixing this. -- |
From @dcollinsnThis /appears/ to be fixed. Taking with the intent to bisect this afternoon. |
From @dcollinsnI can't reproduce this going back to 5.10.0, which is the earliest perl I'm able to build. |
@dcollinsn - Status changed from 'open' to 'resolved' |
From @iabynOn Wed, Jul 06, 2016 at 01:13:39PM -0700, Dan Collins via RT wrote:
The fix bisects to 3 commits, one of which is commit 9850bf2 sort/multicall patch which sounds plausible that it fixed it. -- |
Migrated from rt.perl.org#28438 (status was 'resolved')
Searchable as RT28438$
The text was updated successfully, but these errors were encountered: