Re: DEBUGCHK during IPSM load

From: Paul G. Tobey [eMVP] (ptobey_no_spam_at_instrument_no_spam.com)
Date: 03/30/04 

Date: Tue, 30 Mar 2004 08:09:55 -0700

I don't know this from experience of the source, but my guess is that they
simply have a DebugBreak() explicitly in the IPSM code, so that they
(Intel), can debug it easily. I just hit Run and keep going...

Paul T.

"Trevor Bimler" <anonymous@discussions.microsoft.com> wrote in message
news:DCE4B206-A91C-4DFD-970C-B462DD614254@microsoft.com...
> I'm involved in porting CE to a new platform, using the Accelent PXA255
BSP. Part of the project requirement is for persistent storage in FLASH, so
I integrated the IPSM V3.62 component that's included in the BSP. It loads
and seems to work (hurrah!) in that I can create a directory on the
persistent volume and it does in fact persist across power-offs, but I get a
debug check when the volume is mounted. The call stack is as follows:
>
> PSMFSD!PSMFSD_MountDisk line 163 + 8 bytes
> FSDMGR!InitEx(_FSDINITDATA * 0x0408f1d4) line 172 + 20 bytes
> FSDMGR!AutoLoadFileSystems(unsigned long 0x00000001, unsigned long
0x00000001) line 549
> FSDMGR!InitStorageManager(unsigned long 0x00000001) line 751
> FSDMGR!Init(unsigned long 0x00000001) line 38 + 8 bytes
> FILESYS!InitStorageManager(unsigned long 0x00000001) line 2238
> FILESYS!MountSystemHive(unsigned short * 0x0408fe30) line 623
> FILESYS!prgInitRegistry(int 0x00000000, unsigned short * 0x0408fe30) line
983
> FILESYS!DoGeneralInit(unsigned short * 0x00074594) line 2448 + 12 bytes
> FILESYS!WinMain(HINSTANCE__ * 0x00000000, HINSTANCE__ * 0x0408fe34,
unsigned short * 0x03f45230, int 0x03f40004) line 2846 + 12 bytes
> COREDLL!MainThreadBaseFunc(void * 0x000232f4, unsigned long 0xe1fe2b22,
unsigned long 0x00000000, unsigned long 0x0408fed8, unsigned long
0x00000005) line 402 + 28 bytes
>
> It's doubtless something stupid that I've forgotten to do, but for the
life of me I can't imagine what. Any help would be gratefully accepted.
>
> Trevor Bimler