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 loops infinitely with __DIE__ and DESTROY #9358
Comments
From @pjscottIf you run the following, be prepared to kill it from another window: #!/usr/bin/perl -d sub Foo::new { bless {} , "Foo" } BEGIN { It will print the line Foo::DESTROY(/tmp/foo:4): sub Foo::DESTROY { 1 } repeatedly and be unstoppable from its own window. This goes waaaay back. It behaves as described in 5.10.0, 5.8.8, FWIW: Summary of my perl5 (revision 5 version 10 subversion 0) configuration: Characteristics of this binary (from libperl): |
From @jkeenanOn Fri May 30 10:15:59 2008, Peter@PSDT.com wrote:
I tried this tonight on both Darwin/PPC and Linux/i386, both with Perl Thank you very much. |
The RT System itself - Status changed from 'new' to 'open' |
From @kevindawson$ perl 55084.pl Loading DB routines from perl5db.pl version 1.39_10 Enter h or 'h h' for help, or 'man perldebug' for more help. main::(55084.pl:17): exit(0); Loading DB routines from perl5db.pl version 1.39_10 Enter h or 'h h' for help, or 'man perldebug' for more help. main::(55084.pl:17): exit(0); imho this is was fixed in shlom-fish wake and thus closed |
From @kevindawson |
From [Unknown Contact. See original ticket]$ perl 55084.pl Loading DB routines from perl5db.pl version 1.39_10 Enter h or 'h h' for help, or 'man perldebug' for more help. main::(55084.pl:17): exit(0); Loading DB routines from perl5db.pl version 1.39_10 Enter h or 'h h' for help, or 'man perldebug' for more help. main::(55084.pl:17): exit(0); imho this is was fixed in shlom-fish wake and thus closed |
@iabyn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#55084 (status was 'resolved')
Searchable as RT55084$
The text was updated successfully, but these errors were encountered: