I have compiled perl-5.15.1 and tested with that. The bug is present.
I also implemented your suggestion to add some code to catch the CLONE call. I got:
$ perl -d debugLWPtheads.pl Loading DB routines from perl5db.pl version 1.33 Editor support available. Enter h or `h h' for help, or `man perldebug' for more help. main::(debugLWPtheads.pl:35): exit main(); + DB<1> c Starting a thread to find all SHAs Devel::CLONE called with args [ Devel ] at debugLWPtheads.pl line 9 th +read 1 Devel::CLONE('Devel') called at debugLWPtheads.pl line 23 thread 1 at debugLWPtheads.pl line 9 thread 1 Devel::CLONE('Devel') called at debugLWPtheads.pl line 23 thread 1 This line should be reached without error messages. Debugged program terminated. Use q to quit or R to restart, use o inhibit_exit to avoid stopping after program termination, h q, h R or h o to get additional info. + Thread 1 terminated abnormally: Undefined subroutine &Cwd:: +CLONE called at debugLWPtheads.pl line 23. at debugLWPtheads.pl line 23 thread 1 DB<1> Scalars leaked: 1 Use `q' to quit or `R' to restart. `h q' for details.
It looks like the package of the CLONE call is moving around, as I reported in my original post.
Also, as it looks like this is a genuine bug rather than a mistake on my part, should this discussion be moved to a different part of the Monastery?
In reply to Re^4: Abnormal exit with threads, LWP and the Perl Debugger
by chrestomanci
in thread Abnormal exit with threads, LWP and the Perl Debugger
by chrestomanci
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |