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
call stack bug in perl5 #9679
Comments
From tswr@tswr.ruCreated by tswr@tswr.ruprint 'qq', $y=&{print $x}; Perl Info
|
From @nwc10On Wed, Mar 11, 2009 at 08:20:34AM -0700, wrote:
I don't know if this is the same bug. This is blead, with -DDEBUGGING and -g: $ cat 63790e EXECUTING... => I don't know what's going on. Why is that stack wrong, just before the failing (gdb) call Perl_sv_dump(my_perl, gv) And here's an even terser example: $ cat 63790a EXECUTING... => Nicholas Clark |
The RT System itself - Status changed from 'new' to 'open' |
From @rgs2009/3/11 Nicholas Clark <nick@ccl4.org>:
I think that's due the way that perl sets up calls to an import by |
From support@ActiveState.comHi, Thanks for your email. You are using an out of support version. Your problem may be fixed in the most recent version of ActivePerl in the 5.8 Best regards, Graham Stuart 03/11/2009 08:20 - �ми��ий �о�нев wrote:
PATH=C:\Perl\bin;C:\Perl64\site\bin;C:\Perl64\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program
|
From dioksin@gmail.comanother version of this bug ()=("qwe",$_=&{1==1}); -- Locally applied patches: @INC for perl v5.8.9: Environment for perl v5.8.9: // |
@iabyn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#63790 (status was 'resolved')
Searchable as RT63790$
The text was updated successfully, but these errors were encountered: