FreeBSD Bugzilla – Bug 81289
Options for ucontext/pthread/fork in security/stunnel (ucontext is broken)
Last modified: 2005-06-14 10:11:26 UTC
There are known problems with stunnel's new threading model - ucontext(3),
some of which were reported to ports@ and ports-bugs@ they include
unexpected exits (without errors) and build faulures on sparc64.
See ports@ mailing list, ports/81162 and
Following is a patch to the port that lets the user choose ucontext,
pthread or fork model. It currently defaults to pthread.
This should eliminate the problems as it seems that ucontext is broken,
not 4.10. At first glance I saw that pthread code was not touched
between 4.09-4.10 and it works fine for me with pthreading.
Over to maintainer.
-----BEGIN PGP SIGNED MESSAGE-----
Someone available to commit this?
It has been idling for 19 days. Stunnel is useless without this patch -
it quits after 2 connections because of its brand new (and broken)
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
On Wed, Jun 08, 2005 at 08:00:27AM +0000, Vasil Dimov wrote:
> Someone available to commit this?
> It has been idling for 19 days. Stunnel is useless without this patch -
> it quits after 2 connections because of its brand new (and broken)
> ucontext(3) threading.
Sorry, I've been working on it in the last day or three, trying to
come up with a somewhat more robust patch. Yours is okay for this
particular problem, but I'm thinking of something a bit more configurable;
should be done today.
Peter Pentchev firstname.lastname@example.org email@example.com roam@FreeBSD.org
PGP key: http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553
Thit sentence is not self-referential because "thit" is not a word.
I've committed a slightly modified version. Thanks!