I would try to step through to find which line precisely results in the
error.  In the event of corrupt memory problems (as this seems to be) that
is the only method that I have ever found to work.  Of course, I have not
encountered this particular problem, so this advice may not be worth what
you paid for it.

Paul

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Martin
Elzen
Sent: Wednesday, July 10, 2002 11:15 AM
To: Palm Developer Forum
Subject: best way to debug a 'changed emulated program counter' ?


Hi all.

For the last couple of days I've been working on getting one of our more
important apps to work on the POSE with a debug ROM.  After fixing up some
obvious (and relatively easy to correct) problems, I've now seen the POSE
give an error as follows:

MedEurope (7.24) just changed the emulated program counter to 0xFEFE0000.
This address is invalid because it's in neither ROM nor RAM.

Looking it up in the archives gives me the info that somewhere the program
counter is being corrupted, and that it's most likely due to writing past
the end of a buffer or something similar.  So...  I was wondering, what's
the quickest way to debug this?  Should I increase the size of half of the
arrays used by that form, and see if that appears to help out, and kind of
do a binary search that way to see which array's getting whocked?  Or should
I just step thru all of the functions that are called during the
event-habdling of that form?

Sincerely,
Martin






--
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/

Reply via email to