Hello, Rick McGuire wrote: > The accept() call is the thread where the daemon is waiting for new > in-coming connections. There should be a second thread in the process > that's servicing the request for the hung process. Since the client > process is waiting for a return response, the accept() loop must have > created a connection for that request sufficient for a request to be > written to the socket. > > Rick > > Thats not good...
1. rexx month.rex 2. dbx on rxapi r...@build61 rc:0 # dbx -a 245806 Waiting to attach to process 245806 ... Successfully attached to rxapi. Type 'help' for help. reading symbolic information ... stopped in naccept at 0xd01e1e24 ($t1) 0xd01e1e24 (naccept+0x264) 80410014 lwz r2,0x14(r1) (dbx) thread thread state-k wchan state-u k-tid mode held scope function >$t1 run running 765991 k no sys naccept (dbx) So the only thread running is in naccept... Bye Rainer ------------------------------------------------------------------------------ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
