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

No, I did not get a resolution.

At the moment I am using a work around where if I want to debug the parts of the code that do http requests I run a single threaded version of the script, and if I want to debug the threading stuff, I comment out the http stuff and replace it with dummy placeholder code.

It would be nice to know where the bug lies so that I can report it to the correct place, though seeing as LWP is core, perhaps I should just report it as a bug against perl, and not concern myself with which module is to blame.

Comment on 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 27, 2012 at 11:52 UTC

Perhaps the simplest workaround -- and potentially quick way to trace the origin -- would be to satisfy the missing call:

## somewhere at the top of your application.
BEGIN {
    package Devel;
    use Carp qw[ cluck ];

    sub CLONE {
        cluck "Devel::CLONE called with args [ @_ ]";
    }
}
[download]

That ought to both get you passed the symptom and provide a full trace-back to the originating cause.

You might have to experiment with return values to prevent some error action being taken.

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]
[d/l]


Welcome to the Monastery
	PerlMonks