Hi,

I use a method to generate a dump file on my WinCE6.00 on a USB Storage device.
I copy the .kdmp file to the flat release directory of my OS and open it with platform builder (as described in your document).
I do Target->Attach Device after which I get 2 errors:
- the debugger searches for the ..\coreos\core\thunk directory which is not supplied by Microsoft (so it must be ok)
- the Unhandled exception in COREDLL.DLL wich seems to be no problem as well, according to your text file
I configured the symbol path, just in case, since your document is a little confusing about this item
I do not do source path mapping

The output window looks the following way:

PB Debugger The Kernel Debugger connection has been established (Target CPU is ARM).
PB Debugger Target name: CE Dump File
PB Debugger Probe name: PmDump
PB Debugger
PB Debugger ***** Dump File Info *****
PB Debugger
PB Debugger System Information
PB Debugger ==================
PB Debugger Dump Type : System
PB Debugger OS Version : 6.0.1937.3
PB Debugger LCID : 1033
PB Debugger CPU Architec: 5
PB Debugger CPU Type : 2577
PB Debugger CPU Level : 4
PB Debugger CPU Revision: 4
PB Debugger Machine : 0x01C2
PB Debugger OEM String : Digi ConnectCore 9C
PB Debugger Platform : ConnectCore 9C
PB Debugger Platform Ver: 6.0
PB Debugger
PB Debugger Bucket Parameters
PB Debugger =================
PB Debugger EvntType: WinCE600Exception
PB Debugger AppName : ErrorGeneration1.exe
PB Debugger AppVer : 6.0.0.0
PB Debugger AppStamp: 4ad469d3
PB Debugger ModName : coredll.dll
PB Debugger ModVer : 6.0.0.0
PB Debugger ModStamp: 4ad5c74f
PB Debugger Offset : 0000cc6c
PB Debugger OwnName : ErrorGeneration1.exe
PB Debugger OwnVer : 6.0.0.0
PB Debugger OwnStamp: 4ad469d3
PB Debugger
PB Debugger **************************
PB Debugger
PB Debugger Kernel debugger connected.
PB Debugger Binary Image should be loaded at 0x802c0000 / Data relocated at 0x80d26000
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\NK.EXE'
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\SHELL.EXE'
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\UDEVICE.EXE'
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\UDEVICE.EXE'
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\UDEVICE.EXE'
PB Debugger Loaded 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\RUN_DEBUG.EXE', no matching symbolic information found.
PB Debugger Loaded 'CONMANCLIENT2.EXE', no matching symbolic information found.
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\UDEVICE.EXE'
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\SERVICESD.EXE'
PB Debugger Loaded 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\DIGI_DAEMON.EXE', no matching symbolic information found.
PB Debugger Loaded 'ARTMAIN.EXE', no matching symbolic information found.
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\ERRORGENERATION1.E XE'
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\OLE32.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\WS2.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\WSPM.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\SSLLSP.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\FPCRT.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\TIMESVC.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\TELNETD.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\FTPD.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\HTTPD.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\IPHLPAPI.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\UIPROXY.DLL'
PB Debugger Loaded 'TCPCONNECTIONA.DLL', no matching symbolic information found.
PB Debugger Loaded 'EDBGTL.DLL', no matching symbolic information found.
PB Debugger Loaded symbols for 'C:\WINCE600\ART88\ARTOS-012\ARTOS-012\RELDIR\CCX9C_ARMV4I_RELEASE\TOOLHELP.DLL'
I truncated the output in order to shorten this mail.

From this point on I open the Target Control window to start some analysis. When issuing the "!diagnose all" command I get following message:
:
Windows CE>!diagnose all
Error resolving expression dwId>
ERROR in ReadStruct, can't read {,,kernel.dll}g_pprcNK->dwId
Symbols for NK.EXE are incorrect. Attempting to reload symbols ...
Error resolving expression dwId>
ERROR in ReadStruct, can't read {,,kernel.dll}g_pprcNK->dwId


Unable to resolve NK.EXE symbols.

Is the debugger in a break state?

If not, you must first break into the debugger before attempting to use
debugger extension commands.
What am I doing wrong here?


Regards
Kris






More...