Re: Privoxy crashes on one OpenBSD machine but not another

2020-06-09 Thread Fabian Keil
Sebastien Marie wrote: > A fix has been commited. Great. After applying 009_asr Privoxy's regression tests indeed run without errors. > Thanks for investigated the problem and provided a test case. It was very > useful to properly found the state corruption. You're welcome. Fabian

Re: Privoxy crashes on one OpenBSD machine but not another

2020-06-08 Thread Sebastien Marie
Hi, A fix has been commited. Thanks for investigated the problem and provided a test case. It was very useful to properly found the state corruption. -- Sebastien Marie On Wed, Jun 03, 2020 at 07:22:52PM +0200, Fabian Keil wrote: > TJ wrote: > > > I'm migrating my system configs from one Ope

Re: Privoxy crashes on one OpenBSD machine but not another

2020-06-03 Thread Fabian Keil
TJ wrote: > I'm migrating my system configs from one OpenBSD machine (Pentium 4) to > another (Core 2 Duo). > > I noticed unpredictable crashes of the Privoxy package when run and used > on the C2D computer. These crashes don't occur on the P4 at all, with > the same traffic. I tried to reprodu

Re: Privoxy crashes on one OpenBSD machine but not another

2020-05-04 Thread TJ
> Same DNS setup on the machine, same network speed/latency? If this is a > race condition that could be the difference. Same LAN/DNS, yes. > Anyways, when looking at the privoxy code and their community I got so > discouraged that I realized that for me, it was not worth the risk. I'm getting t

Privoxy crashes on one OpenBSD machine but not another

2020-05-04 Thread TJ
I'm migrating my system configs from one OpenBSD machine (Pentium 4) to another (Core 2 Duo). I noticed unpredictable crashes of the Privoxy package when run and used on the C2D computer. These crashes don't occur on the P4 at all, with the same traffic. Both computers are running the same vers

Re: Privoxy crashes on one OpenBSD machine but not another

2020-05-04 Thread Gabriel Kihlman
Hi, TJ writes: > > I tried launching the daemon from gdb to diagnose the problem, but the > package of course has no debug symbols. When gdb ran it from the > /var/privoxy chroot, the process crashed with a SIGPIPE. When I tested > it running outside the chroot, it crashed with a SIGABRT due to