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
Segmentation fault in recursive FETCH #6314
Comments
From powerman@sky.net.uaCreated by powerman@sky.net.uapowerman:~$ perl -e ' Perl Info
|
From @nwc10On Tue, Feb 18, 2003 at 02:55:41AM -0000, powerman@sky.net.ua (via RT) wrote:
Your test script causes infinite recursion: #470 0x080aa8c5 in S_magic_methpack (sv=0x9cee2b0, mg=0x9cee6c8, and the segmentation fault comes when the perl interpreter exhausts the C What did you expect to happen? The perl script to run to completion in some Nicholas Clark |
From goldbb2@earthlink.netNicholas Clark wrote:
There is a possibly way for the script to run to completion: If, within Curiously, with tied scalars, the variable *does* appear to not be -- |
From enache@rdslink.roOn Sun, Feb 23, 2003 at 02:52:47PM -0500, Benjamin Goldberg wrote:
%main::qwe doesn't appear as tied inside FETCH. When the user says I think the matter is that Perl, just like any other scripting language, I don't even need FETCH to make it dump core; look at this: # perl -e '{ package P; sub TIESCALAR { tie $a, P } } tie $b, P' IMHO, this kind of things cannot be called bugs. Regards Adi |
From powerman@sky.net.uaHi! On Sun, Feb 23, 2003 at 02:57:34PM -0000, Nicholas Clark wrote:
I understand this and put word "recursion" in subject. ;-)
I don't think so - see below.
I expect behaviour like in recursive function call - eat all memory for ---cut--- real 0m0.050s powerman:~$ time perl -e 'sub QWE { QWE() } QWE() ' real 0m16.194s If I rewrite FETCH this way: But this example is working: I understand what such deep recursion is very rare and in most cases abnormal. These strange results may point for some hidden bugs and this is reason -- |
From powerman@sky.net.uaHi! On Sun, Feb 23, 2003 at 08:03:35PM -0000, enache@rdslink.ro (via RT) wrote:
IMHO any kind of things which result in segfault in perl is bugs or ... -- |
From @iabynOn Sun, Feb 23, 2003 at 05:22:37PM +0200, Alex Efros wrote:
The former uses the C stack for the recursive calls; the later uses the -- |
From zefram@fysh.orgThere is no Perl bug here. This ticket should be closed. -zefram |
@tonycoz - Status changed from 'open' to 'rejected' |
Migrated from rt.perl.org#21273 (status was 'rejected')
Searchable as RT21273$
The text was updated successfully, but these errors were encountered: