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
lvalue subs not working inside debugger #4006
Comments
From coyote.frank@gmx.netThe following short program works fine outside the debugger my $x; tested with 5.6.0 and 5.6.1 Perl Info
|
From @floatingatollYour bug is confirmed under 5.7.1 and perl-current as well. A second test R. |
From germain@ebooksfrance.comHere is a simple test case : #!/usr/bin/perl -w When ran through perl 5.6.1 or 5.8.0, this program outputs when ran through perl -d, it outputs We are stuck with this problem for PerlQt (http://perlqt.sourceforge.net) Thanks, |
From @schwernConfirmed this is still a problem in bleadperl and 5.8.5. |
From guest@guest.guest.xxxxxxxxThis problem is caused by the fact that perl wraps each function call to However, perl functions have an internal NODEBUG flag that prevents perl -wle ' nodebug(\&a); This program should print "1" with or without -d. Tuomas
|
The RT System itself - Status changed from 'new' to 'open' |
From houstorx@rpc142.cs.man.ac.ukCreated by houstorx@rpc142.cs.man.ac.ukLvalue functions don't work properly when running under the my $x = 'badbad'; prints 'The value of $x is: badbad' when you run it with the Perl Info
|
From @iabynOn Sat, Jul 02, 2005 at 10:03:42AM -0000, houstorx @ rpc142. cs. man. ac. uk wrote:
The reason is that when running under the debugger, all function calls are if (wantarray) and of course that blows away the lvalue-ness of the value returned by the Can't see an easy way op fixing it. -- |
The RT System itself - Status changed from 'new' to 'open' |
From @smpeters
Actually, this is a old known bug. Merging this one with RT #7013. |
From kynn@panix.comSubs defined with the lvalue attribute are unrecognized or mishandled # test_script.pl my $var = 0; sub foo : lvalue { foo = 1; print "OK: $var\n"; __END__ % perl test_script.pl Loading DB routines from perl5db.pl version 1.28 Enter h or `h h' for help, or `man perldebug' for more help. main::(test_script.pl:4): my $var = 0; Perl Info
|
From kynn@panix.com[ This bug report supersedes #36532, which was mistakenly filed under Subs defined with the lvalue attribute are unrecognized or mishandled # test_script.pl my $var = 0; sub foo : lvalue { foo = 1; print "OK: $var\n"; __END__ % perl test_script.pl Loading DB routines from perl5db.pl version 1.28 Enter h or `h h' for help, or `man perldebug' for more help. main::(test_script.pl:4): my $var = 0; Perl Info
|
From @nwc10Superceded by bug 36534 |
The RT System itself - Status changed from 'new' to 'open' |
From deepfryed@gmail.comCreated by deepfryed@gmail.comThis is a bug report for perl from deepfryed@gmail.com, ----------------------------------------------------------------- http://rt.perl.org/rt3/Public/Bug/Display.html?id=7013 The fix is to patch pp_hot.c and perl5db.pl to call DB::lsub for lvalued subs Devel::DProf and similar modules need to be fixed as well, but thats patch attached Perl Info
|
From dland@landgren.netOn Tue Dec 11 15:25:20 2007, deepfryed@gmail.com wrote:
I confirm that this bug still exists in the current development version We are, however, in a code freeze for the release of Perl 5.10.0, This patch will be addressed at some point soon after that happens. Thanks, |
The RT System itself - Status changed from 'new' to 'open' |
From @smpetersOn Dec 11, 2007 5:25 PM, via RT bharanee rathna
Thanks very much for this patch. Someone should be looking into it Thanks again, Steve Peters |
From deepfryed@gmail.com
Ooops, my @work vimrc, sorry but yes that must be just white space fixes
I will hack one up soon, if you guys have not attempted to write one already |
From @smpetersOn Wed Jan 16 21:51:32 2008, deepfryed@gmail.com wrote:
A separate patch was sent in to provide a TODO test. With the pp_hot.c changes above, the |
@smpeters - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#7013 (status was 'resolved')
Searchable as RT7013$
The text was updated successfully, but these errors were encountered: