Re: privoxy broken with latest i386 snap?

[Chris Kuethe <ckuethe@ualberta.ca>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 13 Feb 2003, Marco S Hyman wrote:

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

my apologies for jumping to conclusions

> It seems that the changes only changed timing to allow an existing bug to
> show up.   Privoxy was hanging on DNS access as part of gethostby* calls
> from multiple threads.  Per POSIX get*by* is NOT thread safe.  get*by*_r
> would be, but we don't have them.
>
> This patch to the privoxy port seems to resolve the problem.  Please apply
> and test.   I *think* it will resolve the problem.   I'm still testing.
> Sometimes it took lots of effort to trigger the bug so if I'm wrong the
> ptoblem could still exist.

the patch applies ok and seems to fix the bug. at least, what i used to
be able to do (checking news.google.com) to wedge privoxy no longer breaks
it. i'll keep poking at it this afternoon, but i think the fix is good.

thanks for looking into this.

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?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (OpenBSD)

iD8DBQE+TBnp8bLxfOPbiw4RAkRCAJ9xJiGAulE/grL8Ir9J77aTDJXThQCguv2t
MycTKkM95MuvHw3ON2gBK7M=
=ahhQ
-----END PGP SIGNATURE-----