Re: Why is there marvellous mistake in the process WinCE starting
- From: "Bruce Eitman \(eMVP\)" <beitmannospam@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 30 Apr 2005 09:12:44 -0400
Most of us have seen a data abort at one time or another. You have a few
options for debugging:
1. Guess where the problem is and add some DEBUGMSGs or RETAILMSGs to
narrow down the cause. You can guess that this is in one of your storage
devices since the problem is in Filesys.exe.
2. Use KITL and the Kernel Debugger to do Just In Time (JIT) debugging.
When the exception occurs, the souce code will pop up in PB and take you to
the line of code that the error occured on.
3. Track the exception data down to the line of code, this is fairly easy,
read on.
Use the data created when you built, this data gives you addesses of DLLs
and Exes, as well as offsets for functions and ultimatly lines of code. I
believe that you want to use the PC value, in your case 800bfeac, as your
Exception Address (EA)
Look up EA in your makeimg output. It falls between two modules code starts
(CS). The one with the lower number is the module with the problem. Then
the offset into the module is EA-CS=MO. Look MO up in <module.map> in your
target folder. Similar to looking it up in the makeimg output, it will give
you the function that caused the exception, and the function offset (FO).
Do the math again MO-FO=IO. Now figure out which c/c++ file contains the
function, look up the function in the corresponding .COD file, and find
IO-8. That is the assembly instruction that caused the exception, look up a
few lines an you will see the c code.
If you don't have the .COD files, set the environment variable WINCECOD=1
and rebuild.
--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net
Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member
"MsLrl" <mailyou_mailyou@xxxxxxxxxxx> wrote in message
news:%23EzbpTVTFHA.3308@xxxxxxxxxxxxxxxxxxxxxxx
> hi, all
> When Wince start£¬the following error appeare in the debug messages£º
>
>
> OEMSetRealTime: Year: 1999, Month: 6, Day: 1, Hour: 12, Minute: 0,
> second: 0 rcn
> r=24852540h
> Data Abort: Thread=941ee5c0 Proc=82236c58 'filesys.exe'
> AKY=00000003 PC=800bfeac RA=800bfd6c BVA=fffffffc FSR=00000007
>
>
> After the error occurs, Wince cann't continue to run¡£Is there anyone
> meet the error?? what cause the error?? and how to debug the error??
>
>
.
- References:
- Prev by Date: Re: File Server on 5.0
- Next by Date: Re: how to promote flash speed
- Previous by thread: Why is there marvellous mistake in the process WinCE starting
- Index(es):
Relevant Pages
|
|
