in reply to Re: Segmentation Fault when using LWP::UserAgent
in thread Segmentation Fault when using LWP::UserAgent

Yes, certainly. I am sorry for not giving enough information.

In case the fault happens while executing regularly (not debugging) Windows opens a pop up window showing the content of the memory and the question whether an error message should be sent to Microsoft.

During debugging the following message is given 

Signal SEGV at C:\strawberry\perl\vendor\lib/LWP/UserAgent.pm line 178
        eval {...} called at C:\strawberry\perl\vendor\lib/LWP/UserAge
+nt.pm line
 177
        LWP::UserAgent::send_request('LWP::UserAgent=HASH(0xc704d4)', 
+'HTTP::Req
uest=HASH(0x121ac6c)', undef, undef) called at C:\strawberry\perl\vend
+or\lib/LWP
/UserAgent.pm line 253
        LWP::UserAgent::simple_request('LWP::UserAgent=HASH(0xc704d4)'
+, 'HTTP::R
equest=HASH(0x121ac6c)', undef, undef) called at C:\strawberry\perl\ve
+ndor\lib/L
WP/UserAgent.pm line 261
        LWP::UserAgent::request('LWP::UserAgent=HASH(0xc704d4)', 'HTTP
+::Request=
HASH(0x121ac6c)') called at C:\strawberry\perl\vendor\lib/LWP/UserAgen
+t.pm line
389
        LWP::UserAgent::get('LWP::UserAgent=HASH(0xc704d4)', 'http://m
+y_server/apache2-default/') called at check_lwp.pl line 9

[download]

Thank you for your help, BrowserUk.

Replies are listed 'Best First'.
Re^3: Segmentation Fault when using LWP::UserAgent
by BrowserUk (Patriarch) on May 28, 2010 at 19:22 UTC
    Windows opens a pop up window showing the content of the memory

    It's been a while since I've seen one, so I don't remember the exact wording or options available, but doesn't it tell which dll or executable actually segfaulted? Also, isn't there an option to have it display the report that would be sent to MS, containing a stack trace and other information?

    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.
[reply]

      That's what I had expected also. I could see which other applications where active (antivirus and the like) but not which dll was loaded and at which particular point the crash happened.

      In the meantime I used Microsoft's process explorer in order to find out which dlls were involved. But either it did not show it or I was unable to see it.

      Do the messages from the debugger tell you anything helpful?

      Regards
[reply]
        Do the messages from the debugger tell you anything helpful?

        Not really. I can follow the trail to where is calls $protocol->request() inside the eval, but that's not particularly informative.

        I'd be interesting to see the contents of that pop-up. If you cannot cut&paste the contents, perhaps you could do a window grab (Alt-printscreen) and paste the image somewhere and post the link?

        Given that this is LWP, which is a widely used module, if this were a general problem, you'd expect to be seeing widespread problems. That we aren't suggests it is a set-up problem with your machine.The most likely cause is that when you've installed or re-installed Perl, somehting has got left behind and is mismatched.I've seen this when doing an uninstall followed by an install to the same directory tree without physically blowing away the remnants of the original install (rd /s \<yourPerlPath>) manually first.

        I'd try installing (AS, because it is what I'm familiar with) Perl into a completely new directory structure and try again.

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

In Section Seekers of Perl Wisdom