libev release candidate

Marcus Chuang fuyuan.chuang at
Tue Dec 31 05:16:31 CET 2013

Marc Lehmann <schmorp <at>> writes:

> On Tue, May 08, 2012 at 11:04:51AM -0500, Brandon Black <blblack <at>> wrote:
> > > another bug... cna you try with this loop:
> > 
> > That one works (or at least, doesn't throw an assert when running my
> > app testsuite w/ EV_VERIFY=3)
> Phew, thanks a lot. Two bugs in such simple code :/

I have a similar case while using libev-4.15. I found libev sometimes didn't 
notify me when one socket is readable in "multiple" connections. Thus, I tried 
to turn on debugging(set EV_VERIFY to 3), then I got this assert message:

ev.c:205: verify_watcher: Assertion `("libev: pending watcher not on pending 
queue", ((loop)->pendings) [(((W)w)->priority - (((0x7f) & 4) ? -2 : 0))][w-
>pending - 1].w == w)' failed.

This assert message is not happened in only one connection. Is my or libev's 
bug? Thanks for your reply.

More information about the libev mailing list