this is exactly the symptom i got when the optimiser on my compiler
got a few things confused and SSL_connect() was thinking a simple
allocation had failed when it had in fact succeeded. i got round that
by building a library without the optimiser flags.
can you do a regular ./configure? if so, just hack the debug flags
into the makefile directly. on my port, it's line 63 of the makefile,
starts with CFLAG =. slap a -g on the end, and you might want to get
rid of any -O flags for good measure, too. then make clean and make
all.
hth
j
I am trying to open a client ssl connection and SSL_connect() is
returning -1 on my HPUX port of my code. Note this exact code
currently works (connects successfully and can send and receive
data) on Linux, SunOS, INTERIX(Windows Services for UNIX).
What I know
SSL_connect() returns -1
errno is 0 immediately after that call
ERR_error_string(ERR_get_error(), NULL) yields no error:
error:00000000:lib(0):func(0):reason(0)
SSL_get_error(ssl, success) yields an error of SSL_ERROR_SYSCALL
What are some steps I can take to troubleshoot the client
connection? I can't do too much to the server and know that it
works fine in the other aforementioned environments. I was looking
into compiling the ssl libraries in debug mode to step through the
SSL_Connect call but get an unsupported system error when trying to
do a ./configure -d to build the debug libraries. Any suggestions
on where to start?
If necessary for any system specific gotchas I may be unaware of my
uname output:
HP-UX ------- B.11.00 U 9000/800 --------- unlimited-user license
Thanks
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
