Hi Keith,
In answer to your question about POSE trace output here are the last few
lines of trace output just after the debugger has hung.
Hope this helps...
Thanks,
Chris
---------------------------------------------
23.323: Exiting SLP::SendPacket.
23.323: Exiting SystemPacket::SendPacket.
23.323: Exiting SystemPacket::RPC.
23.323: Exiting Debug::HandleNewPacket.
23.323: Exiting SLP::HandleNewPacket.
23.333: CTCPSocket::HasUnreadData...
23.333: ...has pending data.
23.333: CTCPSocket::Read...
23.333: ...got 10 of 10 bytes of data.
23.333: CTCPSocket::Read...
23.333: ...got 8 of 8 bytes of data.
23.333: CTCPSocket::Read...
23.333: ...got 2 of 2 bytes of data.
23.333: Entering SLP::HandleNewPacket.
23.333: Received sysPktReadMemCmd packet.
23.333: Entering Debug::HandleNewPacket.
23.333: Entering SystemPacket::ReadMem.
23.333: Entering SystemPacket::SendPacket.
23.333: Entering SLP::SendPacket.
23.333: Sending sysPktReadMemRsp packet.
23.333: CTCPSocket::Write...
23.333: ...writing 16 bytes.
23.333: Exiting SLP::SendPacket.
23.333: Exiting SystemPacket::SendPacket.
23.333: Exiting SystemPacket::ReadMem.
23.333: Exiting Debug::HandleNewPacket.
23.333: Exiting SLP::HandleNewPacket.
23.343: CTCPSocket::HasUnreadData...
23.343: ...has pending data.
23.343: CTCPSocket::Read...
23.343: ...got 10 of 10 bytes of data.
23.343: CTCPSocket::Read...
23.343: ...got 10 of 10 bytes of data.
23.343: CTCPSocket::Read...
23.343: ...got 2 of 2 bytes of data.
23.343: Entering SLP::HandleNewPacket.
23.343: Received sysPktWriteMemCmd packet.
23.343: Entering Debug::HandleNewPacket.
23.343: Entering SystemPacket::WriteMem.
23.343: Entering SystemPacket::SendPacket.
23.343: Entering SLP::SendPacket.
23.343: Sending sysPktWriteMemRsp packet.
23.343: CTCPSocket::Write...
23.343: ...writing 14 bytes.
23.343: Exiting SLP::SendPacket.
23.343: Exiting SystemPacket::SendPacket.
23.343: Exiting SystemPacket::WriteMem.
23.343: Exiting Debug::HandleNewPacket.
23.343: Exiting SLP::HandleNewPacket.
23.674: CTCPSocket::HasUnreadData...
23.674: ...has pending data.
23.674: CTCPSocket::Read...
23.674: ...got 10 of 10 bytes of data.
23.674: CTCPSocket::Read...
23.674: ...got 9 of 9 bytes of data.
23.674: CTCPSocket::Read...
23.674: ...got 2 of 2 bytes of data.
23.674: Entering SLP::HandleNewPacket.
23.674: Received sysPktWriteMemCmd packet.
23.674: Entering Debug::HandleNewPacket.
23.674: Entering SystemPacket::WriteMem.
23.674: Entering SystemPacket::SendPacket.
23.674: Entering SLP::SendPacket.
23.674: Sending sysPktWriteMemRsp packet.
23.674: CTCPSocket::Write...
23.674: ...writing 14 bytes.
23.674: Exiting SLP::SendPacket.
23.674: Exiting SystemPacket::SendPacket.
23.674: Exiting SystemPacket::WriteMem.
23.674: Exiting Debug::HandleNewPacket.
23.674: Exiting SLP::HandleNewPacket.
23.674: CTCPSocket::HasUnreadData...
23.674: ...has pending data.
23.674: CTCPSocket::Read...
23.674: ...got 10 of 10 bytes of data.
23.674: CTCPSocket::Read...
23.674: ...got 34 of 34 bytes of data.
23.674: CTCPSocket::Read...
23.674: ...got 2 of 2 bytes of data.
23.674: Entering SLP::HandleNewPacket.
23.674: Received sysPktRPCCmd packet.
23.674: Entering Debug::HandleNewPacket.
23.674: Entering SystemPacket::RPC.
23.674: Entering SystemPacket::SendPacket.
23.674: Entering SLP::SendPacket.
23.674: Sending sysPktRPCRsp packet.
23.674: CTCPSocket::Write...
23.674: ...writing 46 bytes.
23.724: Exiting SLP::SendPacket.
23.724: Exiting SystemPacket::SendPacket.
23.724: Exiting SystemPacket::RPC.
23.724: Exiting Debug::HandleNewPacket.
23.724: Exiting SLP::HandleNewPacket.
I responded to your similar comments (in "Windows 2000 and POSE") on 2/18
with
the following:
>>Any other ideas on why POSE would hang?
>
>What makes you think this is a Poser problem? IIRC, the problem had to do
>with
>not breaking on PilotMain after CW downloaded your application for
>debugging.
>This could also be a problem with with the CW debugger. I'm not saying that
it's
>*not* a Poser problem; it's just that if you have evidence that leads you
>to
>believe it is, then you should let us know about it.
>
>And why are you asking about the serial port? What has that got to do with
this?
>
>As for tracking down the problem, I'd start with turning on the high- and
>low-
>level debug information logging options. Once the debug process is stalled,
quit
>Poser and examine the logging information. See if the last information
>there
has
>to do with Poser sending a "state" packet to the debugger. This would
>indicate
>that the breakpoint in PilotMain was encountered and that Poser told the CW
>debugger.
-- Keith Rollin
-- Palm OS Emulator engineer
"Chris Yourch" <[EMAIL PROTECTED]> on 02/22/2000 01:11:09 PM
Please respond to "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent by: "Chris Yourch" <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
cc: (Keith Rollin/HQ/3Com)
Subject: debugging and POSE
Hi,
The debugger hangs the 2nd time I run it. What I am doing is starting a
debug session, run my program and then end it. Next, I run the debugger
again and this time the debugger hangs. POSE displays a blank gray screen
and the CW debugger is hung. I am using TCP/IP to connect to POSE, r6 of CW
and 3.0a3 of POSE. The only way to recover and run the debugger again is to
close everything and restart. Also, I need to create a new POSE session
file.
The debug log displays the following before the debugger hangs:
3304711: STARTING gComm->LoadTarget
3307525: FINISHED gComm->LoadTarget
Process Created: address=0x3716a
size=0x48e0
cardID=0
dbID=0x2025f
Thanks,
Chris
Chris Yourch
RIA Group
[EMAIL PROTECTED]
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
