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
Debugger corrupts symbol table munging #9145
Comments
From mjcarman@mchsi.comCreated by mjcarman@mchsi.comThis is a bug report for perl from mjcarman@mchsi.com, ----------------------------------------------------------------- Given the following script: use strict; Run normally, this works as expected. (i.e. it prints 1, 2) When run under the debugger, In the particular case where I noticed this bug the new foo() was a wrapper which called Perl Info
|
From @iabynI can't reproduce this in 5.8.8, but its present in 5.9.4, 5.10.0 and bleed: [davem@pigeon bleed]$ ./perl -d /tmp/p Loading DB routines from perl5db.pl version 1.33 Enter h or `h h' for help, or `man perldebug' for more help. main::(/tmp/p:9): no warnings 'redefine'; |
@iabyn - Status changed from 'new' to 'open' |
From @cpansproutFixed by be1cc45. |
@cpansprout - Status changed from 'open' to 'resolved' |
From @salvaCreated by @salvaIf some function &A::foo is exported to package B becomming &B::foo, then, assigning a new CODE ref to *A::foo also unexpectedly changes B::foo. The funny thing is that getting a reference to B::foo returns a reference to the former function! Debugger session follows: DB<1> sub foo { print "former foo\n" } DB<2> *M::foo = \&foo; DB<3> *foo = sub { print "reformed foo\n" } DB<4> x M::foo Perl Info
|
From @cpansproutOn Wed Jul 06 06:27:52 2011, salva wrote:
This is the same bug as #48332, which was fixed in 5.14.0. |
The RT System itself - Status changed from 'new' to 'open' |
@cpansprout - Status changed from 'open' to 'resolved' |
From @iabynOn Wed, Jul 06, 2011 at 06:27:53AM -0700, Salvador Fandiño wrote:
This appears to have been fixed somewhere between 5.13.4 and 5.13.6 -- |
Migrated from rt.perl.org#48332 (status was 'resolved')
Searchable as RT48332$
The text was updated successfully, but these errors were encountered: