need help on perl.exe crash
[email protected] (p srinivas)
| Newsgroups | perl.win32.vanilla |
|---|---|
| Message-ID | <[email protected]> |
Hi,
I am using strawberry perl and calling the perl.exe with perl script from
command line by creating the service. The perl.exe got crashed on the
setup. Can any one please help me on this how to figure out further on this?
I am using win2k8R2-64BIT windows machine.
Perl version
-----------------
c:\strawberry\perl\bin>perl.exe --version
This is perl, v5.8.8 built for MSWin32-x86-multi-thread
Copyright 1987-2006, Larry Wall
Perl may be copied only under the terms of either the Artistic License or
the
GNU General Public License, which may be found in the Perl 5 source kit.
Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.
Crash dump stack trace details
---------------------------------------------
Microsoft (R) Windows Debugger Version 6.9.0003.113 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\administrator.QA\Desktop\perl crash\memory.hdmp]
User Mini Dump File: Only registers, stack and portions of memory are
available
WARNING: Minidump contains unknown stream type 0x13
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
Windows 7 Version 7600 MP (8 procs) Free x86 compatible
Product: Server, suite: TerminalServer DataCenter SingleUserTS
Debug session time: Mon Jul 5 08:00:01.000 2010 (GMT-7)
System Uptime: 54 days 0:15:25.176
Process Uptime: 0 days 0:03:21.000
.......................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
eax=00000000 ebx=00284208 ecx=76f6657e edx=00000dfc esi=00000002
edi=00000000
eip=76f1fc41 esp=002841b8 ebp=00284254 iopl=0 nv up ei pl nz na po
nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b
efl=00000202
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntdll.dll -
ntdll!NtWaitForMultipleObjects+0x15:
76f1fc41 83c404 add esp,4
0:000> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
*
*
* Exception
Analysis *
*
*
*******************************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
perl58.dll -
*** ERROR: Module load completed but symbols could not be loaded for
perl.exe
***** OS symbols are WRONG. Please fix symbols to do analysis.
***** OS (WOW64 kernel32) symbols are WRONG. Please fix symbols to do
analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ntdll!_PEB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
FAULTING_IP:
KERNELBASE!DebugBreak+2
74624159 cc int 3
EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 74624159 (KERNELBASE!DebugBreak+0x00000002)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 1
Parameter[0]: 00000000
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
PROCESS_NAME: perl.exe
FAULTING_MODULE: 75ae0000 kernel32
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5be02a
MODULE_NAME: KERNELBASE
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint
has been reached.
FAULTING_THREAD: 00000dfc
PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS
LAST_CONTROL_TRANSFER: from 75fb893d to 74624159
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be
wrong.
0028c88c 75fb893d 00000002 75f57af0 0000018e KERNELBASE!DebugBreak+0x2
0028f8d0 75fb8971 00000002 75f57af0 0000018e msvcrt!CrtDbgReportWV+0x2ed
0028f8f0 75fa8f0b 00000002 75f57af0 0000018e msvcrt!CrtDbgReportW+0x1d
0028f918 634dd458 00000005 02df62a8 006b075c msvcrt!get_osfhandle+0xd5
0028fcb8 6346b6f9 00000008 02db6a6c 02b4bebc perl58!win32_select+0x108
0028fd48 6348b0c9 006b3874 006b3874 0028fdd8 perl58!Perl_sortsv+0x3d99
0028fd58 63438054 006b3874 0028fd88 00000001
perl58!Perl_runops_standard+0x19
0028fdd8 634cdffe 006b3874 634c7da0 00000003 perl58!perl_run+0x2a4
0028ff18 00401322 00000003 006b1780 006b1d68 perl58!RunPerl+0xbe
0028ff48 0040124b 00000003 006b1780 006b1d68 perl+0x1322
0028ff78 00401298 00000001 00000000 0028ff94 perl+0x124b
0028ff88 75b5673e 7efde000 0028ffd4 76f514b9 perl+0x1298
0028ff94 76f514b9 7efde000 610acd9b 00000000
kernel32!BaseThreadInitThunk+0xe
0028ffd4 76f51715 00401280 7efde000 ffffffff ntdll!RtlCreateUserThread+0x5d
0028ffec 00000000 00401280 7efde000 00000000
ntdll!RtlCreateProcessParameters+0x4f
STACK_COMMAND: ~0s; .ecxr ; kb
FOLLOWUP_IP:
KERNELBASE!DebugBreak+2
74624159 cc int 3
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: KERNELBASE!DebugBreak+2
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: KERNELBASE.dll
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS_80000003_KERNELBASE.dll!base_address
Followup: MachineOwner
---------