On Sat, Feb 11, 2012 at 12:31 PM, Gilad Benjamini <gbenjam...@juniper.net> wrote: > (re-sending since my previous message doesn't appear to have reached the list) > Our code uses libevent 2.0.10 and we are running into the assertion below. > We haven't seen any real problems beyond that assertion but it is alarming > nevertheless. > > Can anyone please shed some light on what this assertion might indicate ?
So, this assertion means that the backend you're using (e.g., epoll, kqueue, poll, select) has decided that some fd is active, and libevent is trying to activate the events that are waiting on that fd. But not only are no events waiting on that fd ... that fd is higher than any fd for which events were previously added! This probably means there's a bug someplace -- either in your code, or in Libevent. You say that you're using Libevent 2.0.10-stable. That's over a year old; there have been literally hundreds of bugs fixed since then! So before you go any further, I would strongly suggest that you see whether upgrading to the latest 2.0 release fixes your problem. If it doesn't, at least we can rule out the possibility that it is a weird side effect of some other already-fixed problem, which should help track it down. yrs, -- Nick *********************************************************************** To unsubscribe, send an e-mail to majord...@freehaven.net with unsubscribe libevent-users in the body.
