Re: Ooops! Perl interpreter has stopped working

Be specific. State OS, Perl and module versions. A Have you checked the open bug queues for the modules you use? Is there a problem with an underlying library the modules rely on? Any platform specific issues? These are the things I would check first. Then Tutorials -> Debugging and Optimization, oldies but goldies: brian's Guide to Solving Any Perl Problem. Failing that post a small example which can reproduce your problem. How do I post a question effectively?.

Comment on Re: Ooops! Perl interpreter has stopped working

Replies are listed 'Best First'.
Re^2: Ooops! Perl interpreter has stopped working by greenhorn_007 (Acolyte) on Jun 04, 2014 at 09:52 UTC
OS: Windows 7 Enterprise Strawberry Perl (v5.18.2) And I am using wxWidgets, latest from CPAN. I can't really google it, looks like not many people have the "perl interpreter stopped working problem". Because the wxWidgets are written in C++ and in Perl we have some wrapper around them - I suspect the fault is somewhere in the C++ code (some pointer failures)- and some wrong messing with the wrapped functions from my side. Because this "program has stopped working... windows detected problem" etc stuff happens quite a lot when you program C/C++, and I have never really seen them in Perl -that's why I actually asked the first question - how can I get this mesg in general (because I am a curious soul).	[reply]
Re^3: Ooops! Perl interpreter has stopped working by marto (Cardinal) on Jun 04, 2014 at 10:18 UTC
From memory when something dies and Windows reports this sort of error there is a button on the popup which provides further details. This may also be logged in Eventviewer. Using procmon and other tools from the sysinternals suite should aid debugging. Again, have you checked open bugs for the module or the version of wxWidgets being used? Still no example code, while I've never used wxWidgets someone may be able to point out problems.	[reply]