Alan

YES!  I have been having problems with NetLibSelect as well.  I posted a 
problem on Friday where NetLibSelect works for a while and then stops 
reporting that there is data available in the socket.  The system events 
keep working.  We have done some troubleshooting and this is what we have 
found:

1. the socket does not get closed, i.e. it is still valid/available
2. the event loop is still running, it responds to taps but unlike yours we 
never get the FDIsSet on the socket
3. we tried enabling tracing in the NetLib and using NetLibMaster to 
retreive and dump the logs and it looks like at some point the 
socket/network stack just stops telling us there is data.  We see on the 
function trace the app going into and out of NetLibSelect over and over and 
over ...........
4. if we close the app which closes the socket and try to reconnect the call 
to connect fails ( not the call to socket )

It is sounding there there is a possbile bug in the NetLib stack.

spike


>From: Alan hand <[EMAIL PROTECTED]>
>Reply-To: "Palm Developer Forum" <[EMAIL PROTECTED]>
>To: "Palm Developer Forum" <[EMAIL PROTECTED]>
>Subject: Troubles with NetLibSelect in main event loop
>Date: Mon, 11 Jun 2001 11:43:50 -0700
>
>I am having troubles implementing NetLibSelect in my main event loop in
>order to handle both data from a socket and user input.  The problem I am
>experiencing is that NetLibSelect seems (it's a little hard to tell for 
>sure
>since I can't debug on the emulator) to not set the FD for the socket even
>though data is available.  The first time around everything goes fine, and
>some data is read from the socket.  On the next iteration of the loop, even
>though there is still data left to be read (as the read did not read all
>available data) NetLibSelect says that there is nothing to read.  The app
>then hangs in this state until an event comes along (i.e. a pen tap) and
>then for some strange reason NetLibSelect says that data is available and
>the data is read.  This whole process is repeated over and over again, an
>din order for my program to successfully download a large chunk of data I
>must continually tap the screen!  I can't seem to figure out why this is
>happening, and the fact that I can't use the debugger with NetLibSelect and
>sysFileDescStdIn makes my life that much harder.  Has anyone else run into
>similar problems?  Can anyone find anything wrong in my code?
>
>Thanks in advance,
>Alan
>
[snip]
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com


-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/tech/support/forums/

Reply via email to