Re^2: Abnormal exit with threads, LWP and the Perl Debugger

Replies are listed 'Best First'.
Re^3: Abnormal exit with threads, LWP and the Perl Debugger by BrowserUk (Patriarch) on Jan 28, 2012 at 10:28 UTC
I'd still be interested to see the traceback from the call to Devel::CLONE. it might shed some light on why when I try to run your sample above under the debugger, it segfaults before it ever reached the DB prompt. It would also be nice to track the cure of the bug back to the change that fixed it to give us a more sure feeling that it has been fixed and not just moved, With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. The start of some sanity?	[reply]
Re^4: Abnormal exit with threads, LWP and the Perl Debugger by chrestomanci (Priest) on Jan 28, 2012 at 12:04 UTC
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. [download] 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?	[reply] [d/l]
Re^5: Abnormal exit with threads, LWP and the Perl Debugger by BrowserUk (Patriarch) on Jan 28, 2012 at 12:59 UTC
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. Thanks for doing that. This is possibly connected. it looks like this is a genuine bug rather than a mistake on my part, Agreed. should this discussion be moved to a different part of the Monastery? I don't think there is anywhere better. Ignore this, I misread the above: ~~The bottom line is probably that this is now fixed and is unlikely to be easily backported.~~ With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. The start of some sanity?	[reply]
Re^6: Abnormal exit with threads, LWP and the Perl Debugger by chrestomanci (Priest) on Jan 28, 2012 at 18:24 UTC
Re^3: Abnormal exit with threads, LWP and the Perl Debugger by Anonymous Monk on Jan 28, 2012 at 10:17 UTC
and the bug has disappeared, so it looks like someone else has found and fixed it. or it just moved to some other bit of memory	[reply]