Hi!
> 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
>
<Snip>
> 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.
I used to turn profiling on and off in a method that was called from AppEventLoop, but
I didn't turn it on and off continually. I
moved the code that turns profiling on and off into the event-loop now. Unfortunately,
the result is still the same, i.e. hundreds
of profiling entries for the event-loop.
> 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.
It looks like this is the case. What kinds of code sequences does POSE react to? I do
have the source and the corresponding assembly
code of my app. There are a few JSR to invoke other methods, a few BRAs (and BNE,
etc.), and some TRAPs in my event loop. The loop
itself is a do-while-loop, which the compiler turns into a CMP and a BNE statement at
the end of the loop.
Cheers,
Tilo
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
