<br><br><div><span class="gmail_quote">On 1/18/06, <b class="gmail_sendername">Michal Trojnara</b> <<a href="mailto:Michal.Trojnara@mobi-com.net">Michal.Trojnara@mobi-com.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wednesday 18 of January 2006 15:19, Bart Somers wrote:<br>> We recently ran in to a problem using stunnel on our AIX 5.2 machines.<br>[cut]<br>> stunnel 4.11 on powerpc-ibm-aix5.2.0.0 UCONTEXT+POLL+IPv4 with OpenSSL
<br>> 0.9.8 05 Jul 2005<br><br>I'd try to:<br>1. Upgrade stunnel to version 4.14.<br>2. Try to monitor it with "truss" command.<br>3. Try another threading model<br> ./configure --with-threads=model<br> to select threading model (ucontext/pthread/fork)
</blockquote><div><br>
<br>
<br>
I upgraded to 4.14 and builded stunnel with all three threading models:<br>
<br>
1) ucontext gave the same problem as the above mentioned 4.11 ucontext version<br>
2) pthread gave me a strange error during the "./config" phase:<br>
<br>
checking pthread.h usability... no<br>
checking pthread.h presence... yes<br>
configure: WARNING: pthread.h: present but cannot be compiled<br>
configure: WARNING: pthread.h: check for missing prerequisite headers?<br>
configure: WARNING: pthread.h: see the Autoconf documentation<br>
configure: WARNING: pthread.h: section "Present But Cannot Be Compiled"<br>
configure: WARNING: pthread.h: proceeding with the preprocessor's result<br>
configure: WARNING: pthread.h: in the future, the compiler will take<br>
precedence<br>
configure: WARNING: ## ------------------------------
<div id="mb_0">---- ##<br>configure: WARNING: ## Report this to the stunnel lists. ##<br>configure: WARNING: ## ---------------------------------- ##<br>checking for pthread.h... yes<br>
<br>
After this, i couldn't build the software in the "make" phase. I'm
sorry i forgot to capture that error, but it came from the pthread.h
header file. I'll capture the entire error next week if you're
interested. <br>
For the time being i'm also looking for another build-machine, because
i'm not sure this problem can be caused by an old version of GCC (2.9,
shame).<br>
<br>
3) the fork option builded nicely, no warnings whatsoever, but has the
same behaviour as the ucontext build, crashes with both syslog and
engine=chil enabled.<br>
<br>
I haven't had the possibility to use truss on the binary's, hopelfully i'll try that next week.<br>
</div>
</div>Thanks for your information so far, if i have any news, i'll post it here.<br>
<br>
Best regards,<br>
<br>
Bart Somers<br></div>