help/tips for debugging missing T_GODATA msgs.
help/tips for debugging missing T_GODATA msgs.
- Subject: help/tips for debugging missing T_GODATA msgs.
- From: Doug Hill <email@hidden>
- Date: Thu, 30 Oct 2003 12:23:06 -0500
Hey gang.
I have a Carbon app. on OS X 10.x using OpenTransport and have run into a
problem. My app. is transferring a large file to another computer and
eventually gets into a flow control situation [i.e. OTSnd() returns
kFlowErr]. My code currently does the right thing and waits for a T_GODATA
msg. before resuming sending.
However, in one particular and highly repeatable case my transfer stops.
Looking at my logging my application is sitting waiting for a T_GODATA and
my receiver is waiting for some data. So, evidently I either missed a
T_GODATA msg. or I never received one.
Looking at the EtherPeek packet traces I do see a "window update" TCP packet
from the receiver to the sender which, if I understand correctly, should
cause a T_GODATA to be sent.
I also have code to handle the weird case were you call OTRcv, get a
OTLookErr and then get the T_GODATA by calling OTLook().
what I'm wondering is this; is there any way to debug this at a lower level
to see if I'm just missing this T_GODATA msg. or whether I never got one?
-doug
ps. Adding a hack to periodically send and not wait for a T_GODATA fixes my
stall so I'm fairly confident that I'm on the right track...
--
"Weaseling out of things is what separates us from the animals.
Well, except the weasel."
- Homer J Simpson
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.