Dear all of you,
[I'm the upstream]
I've just spent half an hour trying to reproduce this bug under
valgrind, from two different machines. No luck, it's probably
a timing-dependent heisenbug.
If you're running on x86 or AMD64, could you please try reproducing it
under valgrind? After recompiling Polipo without optimisations,
make CDEBUGFLAGS=-g
run it as so:
su proxy -c 'valgrind --db-attach=yes ./polipo'
When polipo does something wrong, valgrind will dump you into the
debugger, at which point your backtrace-producing skills will be
helpful.
Thanks for your help,
Juliusz
P.S. Hmm, oughtn't we invite somebody who doesn't have a slavic name
to participate in this thread?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
