Re: privoxy broken with latest i386 snap?

[Chris Kuethe <ckuethe@ualberta.ca>]

marc, just in case you don't read ports@ ...

On Mon, 10 Feb 2003, Dan Weeks wrote:

> >>>>> "CK" == "Chris Kuethe" <ckuethe@ualberta.ca>:
> CK> On Mon, 10 Feb 2003, Dan Weeks wrote:
> CK>
> >> i'm home now and I can see it stopping on a -current build from this
> >> afternoon.   Strangely it will keep accepting requests, but then does
> >> nothing after that.  Still digging.
> CK>
> CK> methinks its the recent changes to threads - i'm tempted to try rebuilding
> CK> libpthread with the last changes backed out in hopes that that will help.
>
> if you do please keep us informed.  I'm going to dig without trying that
> for now.

threads are b0rked. backing out marc's changes to the following versions
makes privoxy work again:

uthread_close.c         1.8
uthread_dup.c           1.3
uthread_dup2.c          1.5
uthread_fcntl.c         1.6
uthread_fd.c            1.16
uthread_init.c          1.27
uthread_private.h       1.43

> Thanks for beating on this too.

i wouldn't go near the commercial internet with someone else's browser
on a 20 foot pole without something like privoxy...

CK

-- 
Chris Kuethe, GCIA CISSP: Secure Systems Specialist - U of A CNS
      office: 157 General Services Bldg.    +1.780.492.8135
              chris.kuethe@[pyxis.cns.]ualberta.ca

     GDB has a 'break' feature; why doesn't it have 'fix' too?