Chris,
No, can you tell me how to do that. That would probaly be better then
putting a bunch of error msg calls in the code.
--
Scott Erickson
Software Development Team, FB-4, Inc.
[EMAIL PROTECTED]
"Chris Brooks" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Scott
>
> Have you tried putting the device in debug mode, and using it as the debug
> target?
>
> Chris.
>
>
> ----- Original Message -----
> From: Scott Erickson <[EMAIL PROTECTED]>
> Newsgroups: palm-dev-forum
> To: Palm Developer Forum <[email protected]>
> Sent: Monday, April 25, 2005 3:14 PM
> Subject: error checking and debuging on the device
>
>
>> Hi,
>> I have been trying to find a simple way to do error checking on the
>> device. I tried to use the functions in the error
>> manager(ErrNonFatalDisplayIf()) to just simply output a msg to tell me
> where
>> the program is. They simply dont work. I have the first arg set to
>> true,
>> so it always is called, and a simple msg in the 2nd arg. at runtime, the
>> msg never pops up. What I am trying to do is find out where my code is
>> locking up. It doesnt lock up on the simulator, but it does on the
> device.
>> I want to be able to step through the code in the section it is locking
>> up
>> in so i can find out what function call is making it lock up. Can anyone
>> give me some pointers on an easy way to do this???
>> --
>>
>>
>> Scott Erickson
>> Software Development Team, FB-4, Inc.
>> [EMAIL PROTECTED]
>>
>>
>>
>> --
>> For information on using the Palm Developer Forums, or to unsubscribe,
> please see http://www.palmos.com/dev/support/forums/
>
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please
see http://www.palmos.com/dev/support/forums/
