Laurens <[EMAIL PROTECTED]> wrote:
> How can I tell the GDB debugger (PRC Tools) not to break in PilotMain?
http://prc-tools.sf.net/cgi-bin/info/Palm+OS-specific+GDB+features
> I'm running Gremlins in POSE to stress test my app. One bug occurs
> somewhere between step 2000 and 3000 and I want to pinpoint the line
> where it happens. However, the Gremlin taps the Find function (in the
> silkscreen area) at least two dozen times before I get to the bug,
> forcing me to manually "continue" everytime the OS calls PilotMain.
Once you're using "handle SIGSTOP nostop", GDB won't require manual
assistance every time through PilotMain(). Unfortunately you may find
instead that the *gremlin* stops each time, requiring a manual tap on
"resume" in Poser's dialog box.
At
http://www.escribe.com/computing/pcpef/m4386.html
you'll find a pointer to a one-line Poser patch that stops the gremlin
from tripping over each time, and also a clever trick which can be
summarized for you as "only attach GDB after 1950 or so events, so
hopefully it'll only go through PilotMain() a couple of times (but
more than zero) while the debugger is connected".
> Alternatively, is there a way to disable the Find function in POSE, or
> instruct the Gremlin not to tap there?
#ifdef DEBUG_BUILD
if (HostGremlinIsRunning () && event_is (vchrFind))
eat_event ();
#endif
or words to that effect, probably.
John
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
