On 02/06/2012 04:46 PM, Adrian Chadd wrote:
Hi,
the standard trick:
* designate one thread as "signals here" and block signals on all other threads;
* use pipes for sending signals between threads (ie, to wake them up);
* wish that kqueue and similar methods were portable.
The kqueue API has
On Mon, Feb 06, 2012 at 01:46:59PM -0800, Adrian Chadd wrote:
> Hi,
>
> the standard trick:
>
> * designate one thread as "signals here" and block signals on all other
> threads;
> * use pipes for sending signals between threads (ie, to wake them up);
> * wish that kqueue and similar methods wer
Hi,
the standard trick:
* designate one thread as "signals here" and block signals on all other threads;
* use pipes for sending signals between threads (ie, to wake them up);
* wish that kqueue and similar methods were portable.
adrian
*
On 1 feb 2012, at 23:31, Nick Mathewson wrote:
> … [ questions about POSIX signals and pthreads ] …
> …
> Sadly, this whole business is a huge pile of gunk.
Thanks for the epic reply, Nick.
I did some additional research before diving into my POSIX signal plan and it
indeed looks like a huge mes
On Mon, Dec 19, 2011 at 11:00 PM, Mark Ellzey wrote:
> On Mon, Dec 19, 2011 at 09:57:08PM -0500, Nick Mathewson wrote:
>> I agree with the part of your fix where we don't ignore the extra data
>> whose presence is indicated by a nonzero SSL_pending.
>>
>> But I think these fixes all have some pro
