Personally (and I realize that these techniques may only work for me, but
they're all I can offer) there are two things I'd do:
* Use a version of PalmDebugger that works with Poser. I modified PalmDebugger a
while back to talk with Poser via the same communications that the CodeWarrior
debugger does. I don't think we've released this version of PalmDebugger, but
rumor has it that it will see the light of day *sometime*! Anyway, with it, you
can just type "att" to break into the debug mode.
* Run Poser under the VC++ or CodeWarrior debugger. If Poser hangs, then you may
be able to determine why and attack the problem that way.
An additional recourse now occurs to me:
* Send me your application, tell me how to reproduce the hang you're seeing, and
tell me to figure out why Poser is hanging and fix it!
-- Keith Rollin
-- Palm OS Emulator engineer
Jouni Mannonen <[EMAIL PROTECTED]> on 08/26/99 02:56:54 AM
Please respond to [EMAIL PROTECTED]
Sent by: Jouni Mannonen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (Keith Rollin/HQ/3Com)
Subject: How can I DEBUG into a running application? (Was: How can I Break a
Running Application?)
On a related topic;
I am running into a hard-to-reproduce hang problem that will completely
halt both the Palm device and the POSE emulator when it occurs. This is
extremely irksome to track down since I do not know why or where in the
code it happens and it can take a minute to run with random gremlins to
trigger.
In the PC environment I would simply break into the debugger once the hang
happens and see the call context and disassembly with source; what can I
do to introduce a manual breakpoint in this manner at run time for Palm
or POSE?
Jouni
--
Jouni Mannonen
SurRender3D.com
