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
death during unwinding causes crash #14614
Comments
From zefram@fysh.orgCreated by zefram@fysh.org$ cat t1 The essence of this situation is that non-local unwinding is invoked On pre-5.20 perls, the second exception propagates in a sane manner. On 5.20, things get screwed up. The order in which things get unwound I believe this is down to commit 2537512, Perl Info
|
From zefram@fysh.orgI suspect that the simple solution to this will be to perform the CvDEPTH -zefram |
From @cpansproutThis is related to #105916. -- Father Chrysostomos |
The RT System itself - Status changed from 'new' to 'open' |
From @cpansproutOn Wed Mar 25 01:09:36 2015, zefram@fysh.org wrote:
Not only that, but catching longjmps that occur during leave_scope is probably necessary, too, but that would have to wait until after 5.22. -- Father Chrysostomos |
From perl@profvince.comLe 27/03/2015 17:40, Father Chrysostomos via RT a écrit :
By the way, I would like to note that commit 2537512 ("[perl #119311] (The test suite does not cover the interaction with the debugger, so it Vincent |
From @iabynOn Fri, Mar 27, 2015 at 06:29:17PM -0300, Vincent Pit (VPIT) wrote:
I've pushed the following for smoking: commit f45d6b6 RT #124156: death during unwinding causes crash -- |
From @iabynOn Fri, May 08, 2015 at 10:11:47PM +0100, Dave Mitchell wrote:
and now an even more improved version, currently smoking as The previous version skipped too much on the second POPSUBbing of a There are still many flaws in the current implementation. For example sub Foo::DESTROY { die } will cause Bad Things to happen still. I plan to do a more general fix -- |
From @rjbsOn Mon May 11 05:59:41 2015, davem wrote:
Are we good to apply this? The only smoke issues I see are with George's clang 4.2.1, which shows this error on unwind3, which I did not see /lately/ on blead: http://perl5.test-smoke.org/report/34399 Assuming this is unrelated and/or glitchy, I'd like to apply so that we're in shape for a Monday-ish RC1. -- |
From @khwilliamsonOn 05/15/2015 03:48 PM, Ricardo SIGNES via RT wrote:
commit 1956db7 RT #124156: death during unwinding causes crash |
From @rjbs* Karl Williamson <public@khwilliamson.com> [2015-05-15T18:52:49]
Whoops, I hadn't pulled in a bit. In my defense, I wasn't *that* out of date: Commit: David Mitchell <davem@iabyn.com> :-) -- |
From @khwilliamsonOn 05/15/2015 08:07 PM, Ricardo Signes wrote:
I can understand your confusion, since it stayed on the blocker list; |
From @iabynOn Mon, May 11, 2015 at 01:59:00PM +0100, Dave Mitchell wrote:
Now done as part of my "revamp context system" work. -- |
@iabyn - Status changed from 'open' to 'pending release' |
From @khwilliamsonThank you for submitting this report. You have helped make Perl better. Perl 5.24.0 may be downloaded via https://metacpan.org/release/RJBS/perl-5.24.0 |
@khwilliamson - Status changed from 'pending release' to 'resolved' |
Migrated from rt.perl.org#124156 (status was 'resolved')
Searchable as RT124156$
The text was updated successfully, but these errors were encountered: