-
Notifications
You must be signed in to change notification settings - Fork 559
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
nested eval/sub segfaults #5585
Comments
From root@schmorp.deCreated by root@cerebro.laendleThe following program segfaults with perl-devel and 5.6.1, but not with $eval = eval 'sub { eval "sub { %S }" }'; here is a backtrace: the immediate cause seems to be that S_pad_findlex tries to access an Perl Info
|
From @vanstynMarc Lehmann <root@schmorp.de> wrote: At the point of coredump, pad_findlex() has followed the CvOUTSIDE chain I suspect the problem is this point here: Sarathy, can you shed any light? Hugo |
From @gsarOn Tue, 02 Jul 2002 18:00:49 BST, Hugo van der Sanden wrote:
That test snippet doesn't coredump with perl-5.6.x-current. Perhaps Sarathy |
From @gsarOn Tue, 02 Jul 2002 12:09:30 PDT, Gurusamy Sarathy wrote:
change#16359 also looks relevant. I thought all the 5.6.x changes made it into 5.8.0, but now I'm Sarathy |
From @jhi
I grabbed a new sharp tuit spade and went out to the fields to dig -- |
From [Unknown Contact. See original ticket]On Sun, Jul 07, 2002 at 09:36:40PM +0300, Jarkko Hietaniemi <jhi@iki.fi> wrote:
I installed DEVEL17411 and found that my testcase works fine, but perl [Sat Jul 6 19:47:36 2002] [warn] Warning[8496]: Scalar found where operator expected at mercury::2_709::edit line 1, near "#line 1 "mercury:: which gets reported as a warning (but is an error), immediately followed by the same message as an error message. undef'ing $SIG{__DIE__} and $SIG{__WARN__} seem to improve stability a (btw, all my reported bugs have been fixed really quickly, thanks a lot to #0 0x400f295c in memcpy () from /lib/libc.so.6 -- |
From @jhiSince the original test case seems to be happy with Perl 5.8.0, I'm marking the problem ticket as resolved. (Maybe I'll add the test case to the Perl test suite while I'm at it.) |
@jhi - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#9728 (status was 'resolved')
Searchable as RT9728$
The text was updated successfully, but these errors were encountered: