If i set a readtimout to the dialog (or server) socket, when the timeout happens, the server crashes with SIGSEGV, as described in
http://pocoproject.org/forum/viewtopic.php?uid=23286&f=12&t=6100&start=0
When there is a timeout, receiveBytes from SecureStreamSocket returns -2 (Poco::Net::SecureStreamSocket::ERR_SSL_WANT_READ).
The SEGV seems to be because refill() from DialogSocket will then "refill" the DialogSocket with -2 bytes, and crash.
If i set a readtimout to the dialog (or server) socket, when the timeout happens, the server crashes with SIGSEGV, as described in
http://pocoproject.org/forum/viewtopic.php?uid=23286&f=12&t=6100&start=0
When there is a timeout, receiveBytes from SecureStreamSocket returns -2 (Poco::Net::SecureStreamSocket::ERR_SSL_WANT_READ).
The SEGV seems to be because refill() from DialogSocket will then "refill" the DialogSocket with -2 bytes, and crash.