|Think about Loose Coupling|
Re^7: PANIC: underlying join failed threded tcp serverby BrowserUk (Pope)
|on Oct 19, 2012 at 03:01 UTC||Need Help??|
None of that info is particularly helpful to me at least but if you see something I don't, I'm all ears.
What I can see from that info is:
What that indicates is that either:
The next thing I would try is adding a similar trace line at the end of S_ithread_create(), something like:
And also in
The idea is to isolate whether -- when the error occurs -- the invalid handle is to a thread that has already been freed -- in which case the bug is in threads::list() -- or to a thread that has not yet been freed -- in which case it would mean an OS error of some kind; perhaps resource constraint;
I breifly looked at trying to run your server here and trying to re-create the failure. Whilst the server runs and accepts connections from a telnet seesion, it won't accept input from it because (my) telnet sends character by character and it is expecting entire commands wrapped in your (incredibly complicated) comms protcol.
There is no way I am going to be able to reverse engineer a client that can talk that protocol.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.