r8602 | ajc | 2010-06-02 12:30:25 -0400 (Wed, 02 Jun 2010) | 1 line
Changed paths:
M /trunk/webcit/serv_func.c
* more error logging
r8603 | ajc | 2010-06-02 12:54:28 -0400 (Wed, 02 Jun 2010) | 1 line
Changed paths:
M /trunk/webcit/serv_func.c
* More logging. Also display an error to the user if we get a citserver
greeting other than 200 or 571.
This really is a bizarre bug. Maybe it's some sort of race condition. What
I can tell you is that sometime between when we fetch the server greeting
(always a 200 ready) and when we call get_serv_info(), the server socket dies.
If you run it in the debugger you get a SIGPIPE.
r8604 | ajc | 2010-06-03 00:51:44 -0400 (Thu, 03 Jun 2010) | 1 line
Changed paths:
M /trunk/webcit/serv_func.c
* Removed the extra debug messages. I am about to give up on this problem.
Look for today's date
There is just no sensible explanation for this. One moment we're reading
the server greeting, the next moment the socket is toast. citserver doesn't
provide an explanation either.
