QT SSL handshake error when OpenSSL reporting successful handshake

On a TI OMAP 3530, running Windows CE 6, R2/R3, and QT 4.5.2 or 4.6.2 in a static build configuration, attempting to call connectToHostEncrypted is resulting in a onHandshakeError signal. Using the same QT code, OpenSSL version, and OS dependencies, this succeeds on a slower, PXA320 CPU. Have reproduced this issue using OpenSSL .9.8.L and .9.8.M. From OpenSSL debug, it can be seen that QT is calling SSL_get_error in a polling fashion. For several seconds, OpenSSL returns SSL_ERROR_WANT_READ. Finally, SSL_connect() returns 1, and QT reports SSLHandshakeFailedError.

In the passing scenario, from the PXA320, after SSL_get_error returns 1, two subsequent calls to SSL_read can be seen, followed by some more polling of status, and a successful connection reported by QT. Am thinking this may be somewhat related to timing, as the OMAP 3530 is a pretty high performance CPU. This bug is effecting a product under development by our compay which relies on SSL communication and QT for the user-interface. Please contact me for additional information if you cannot reproduce this. Will be happy to assist in which ever way I can. Thanks,

Nick Velado
nfvelado@marketspectruminc.com