Tilo,
Where are you turning profiling on and off? If it's in a function
subordinate to AppEventLoop, then Poser's profiling routines may not
be able to fold the return calls to AppEventLoop. That is, Poser
doesn't always keep track of time spent in a function in a single
record devoted to that function. Poser tries to distinguish between
function Moe() calling function Curly() and function Larry() calling
function Curly(). For that reason, there could be multiple records
for function Curly() in Poser's lists. It's possible that multiple
entries for AppEventLoop are being created if you continually turn
profiling on and off in a subroutine called by AppEventLoop.
Or perhaps your loop is looping using a code sequence that Poser is
interpreting as a "branch to subroutine". But without seeing your
application myself, I couldn't say that was happening for sure.
-- Keith Rollin
-- Palm OS Emulator engineer
At 11:18 PM +0200 3/29/01, Tilo Christ wrote:
>Hello!
>
>I am using the profiling version of POSE 3.1 (Emulator_profile.exe). I
>use the host functions to activate profiling. Unfortunately, POSE counts
>every iteration through my applications main event-loop as a recursive
>method call (it is actually a while-loop). This results in an overflow
>of the maximum recursion depth rather quickly. What might cause this
>strange behavior?
--
-- Keith Rollin
-- Palm OS Emulator engineer
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
