I've been working on making gevent use libevent's getaddrinfo and
occasionally get the above message in one of the test cases. What
could trigger it? How can I avoid it?
I don't call evdns_getaddrinfo_cancel if the callback was already
executed, so I wonder how could I arrive at invalid request?
Indeed SOCK_DGRAM
> -Original Message-
> From: owner-libevent-us...@freehaven.net [mailto:owner-libevent-
> us...@freehaven.net] On Behalf Of William Ahern
> Sent: Tuesday, November 02, 2010 12:50 PM
> To: libevent-us...@freehaven.net
> Subject: Re: [Libevent-users] Read failures on Unix s
On Tue, Nov 02, 2010 at 03:13:02PM -0400, Simon Perreault wrote:
> On 2010-11-02 14:56, Gilad Benjamini wrote:
> > - Open a Unix socket
> > - Bind to a socket in the file system
> > - Add an event with EV_READ and EV_PERSIST
> > - Wait for events
> > - When an event arrives, call recvfrom on the so
On 2010-11-02 14:56, Gilad Benjamini wrote:
> - Open a Unix socket
> - Bind to a socket in the file system
> - Add an event with EV_READ and EV_PERSIST
> - Wait for events
> - When an event arrives, call recvfrom on the socket waiting for a fixed
> size of ~1800 bytes
Aren't you supposed to listen
I have a simple piece of code which used to work with libevent 1.4 and now
fails with 2.x
The basic operation
- Open a Unix socket
- Bind to a socket in the file system
- Add an event with EV_READ and EV_PERSIST
- Wait for events
- When an event arrives, call recvfrom on the socket waiting for a f
