Welcome to the Monastery | |
PerlMonks |
ActivePerl dies in msvcrt.dll under Windowsby hawtin (Prior) |
on Nov 28, 2005 at 13:52 UTC ( [id://512176]=perlquestion: print w/replies, xml ) | Need Help?? |
hawtin has asked for the wisdom of the Perl Monks concerning the following question: I am having difficulty running a script under ActivePerl 5.8.7 (both build 813 and 815). Running normally it works perfectly but under the debugger (i.e. with -d) I get a message "Perl Command Line Interpreter has encountered a problem and needs to closed. We are sorry for the inconvenience... Please tell Microsoft about this problem" The error message blames a Microsoft DLL: AppName: perl.exe AppVer: 5.8.7.815 ModName: msvcrt.dll ModVer: 7.0.2600.2180 Offset: 000373dc The msvcrt.dll has FileVer: (7.0:2600.2180) and ProdVer: (6.1:8638.2180). I am running Windows XP Professional Version 2002 Service Pack 2. Has anyone else seen this? Is there something I can do? I am not a Windows expert, but the DLL would seem to control the virtual terminal (in which I am running the script of course). The msvcrt.dll appears to have been upgraded recently (my company practices remote upgrading of our systems, probably to stop us getting bored). I thought I could use the previous msvcrt.dll under which I never saw the error, but I can't get perl to use a different version from the OS, and if I change the one in the windows directory the OS refuses to startup. Very occasionally instead of a Windows crash I get a debugger message: Malformed UTF-8 character (unexpected continuation byte 0x97, with no preceding start byte) in substitution iterator at C:/Perl/lib/Carp/Heavy.pm line 61. Malformed UTF-8 character (unexpected non-continuation byte 0x03, immediately after start byte 0xc8) in substitution iterator at C:/Perl/lib/Carp/Heavy.pm line 61. ... Originally I thought that the XML parsing (done via XML::SAX) was causing the problem so I put in code to check all the XML as it was being read, but that had no effect. Switching between XML::SAX::Expat and XML::SAX::ExpatXS caused the place where the problem manifested to change but didn't fix it. I now think that the loading of shared libraries is moving the bug so this message is a red herring. Can anyone shed any light?
Back to
Seekers of Perl Wisdom
|
|