Hi,
On Tue, Mar 26, 2013 at 2:22 AM, sven falempin wrote:
> using libevent2 (libevent-2.0.21-stable) i create this log:
>
> [warn] event_del: event has no event_base set.
> [err] event_assign called on an already added event 0x84de9e4 (events: 0x0,
> fd: 0, flags: 0x0)
>
> using this code:
>
> vo
On Tue, Mar 26, 2013 at 10:04 AM, Azat Khuzhin wrote:
> Hi,
>
> On Tue, Mar 26, 2013 at 2:22 AM, sven falempin
> wrote:
> > using libevent2 (libevent-2.0.21-stable) i create this log:
> >
> > [warn] event_del: event has no event_base set.
> > [err] event_assign called on an already added event 0x
On Tue, Mar 26, 2013 at 10:41 AM, sven falempin wrote:
> Never saw
> i was used to libevent 1
> when i switch to 2
My guess is that you're setting up these events before constructing an
event_base or calling event_init. That might have worked with libevent
1, but in libevent 2, you need to make s
On Tue, Mar 26, 2013 at 10:44 AM, Nick Mathewson wrote:
> On Tue, Mar 26, 2013 at 10:41 AM, sven falempin
> wrote:
> > Never saw
> > i was used to libevent 1
> > when i switch to 2
>
> My guess is that you're setting up these events before constructing an
> event_base or calling event_init. That
Hello all,
I am having significant issues with (near immediate) deadlock when trying to
send data out a single openssl bufferevent from two separate threads. The
individual threads themselves send complete messages with each write. This
should present no real problem from a synchronization pers
Hi
I've run into an issue and I'm wondering if it's expected behavior or not.
If a bufferevent with a configured read-high-watermark actually reaches the
watermark, the TCP disconnect on the underlying socket is not reported. I've
observed this on Mac OS X (kevent) as well as linux 3.5 (epoll
On Tue, Mar 26, 2013 at 10:31 PM, Mina Naguib
wrote:
>
> Hi
>
> I've run into an issue and I'm wondering if it's expected behavior or not.
>
> If a bufferevent with a configured read-high-watermark actually reaches the
> watermark, the TCP disconnect on the underlying socket is not reported. I'v
