2010/9/21 Gilad Benjamini :
[...]
> Any chance you can make something out of the attached log ?
That's pretty helpful! It's almost but not quite enough information
to figure out what's up here. There are a couple of epoll debugging
messages that don't give enough detail.
I just added a couple
On 2010-09-21 08:15, W.C.A. Wijngaards wrote:
> Perhaps you can get EPIPE "Broken Pipe" more easily; fork then kill that
> process involved in the pipe, that sort of thing.
I don't see EPIPE in the list of possible error codes for accept()...
But it's true that other errors would be easier to tri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Nick,
On 09/21/2010 03:31 AM, Nick Mathewson wrote:
>> Having no idea what your test harness is capable of, couldn't one set
>> ulimit -n some_low_value, start a listener, create connections until the
>> error callback is called, and then ...?
>
>
On 2010-09-20 21:31, Nick Mathewson wrote:
>> Also, I noticed a small typo:
>>
>> -void evconnlistner_set_error_cb(struct evconnlistener *lev,
>> +void evconnlistener_set_error_cb(struct evconnlistener *lev,
>
> Thanks. Should I expect a revised patch, or should I try to remember
> to fix this up
