[Libevent-users] calling bufferevent_free within it's own event (version 2.0.21).

To: "libevent-users@xxxxxxxx" <libevent-users@xxxxxxxx>

Subject: [Libevent-users] calling bufferevent_free within it's own event (version 2.0.21).

From: Tomer Heber <tomer@xxxxxxxxxxxx>

Date: Mon, 29 Jul 2013 06:55:09 +0000

Accept-language: en-US

Delivered-to: archiver@xxxxxxxx

Delivered-to: libevent-users-outgoing@xxxxxxxx

Delivered-to: libevent-users@xxxxxxxx

Delivery-date: Mon, 29 Jul 2013 03:10:21 -0400

Reply-to: libevent-users@xxxxxxxxxxxxx

Sender: owner-libevent-users@xxxxxxxxxxxxx

Thread-index: Ac6MKGRY8jeIcK4TQO6t1YTu75AyMw==

Thread-topic: calling bufferevent_free within it's own event (version 2.0.21).

Hi,

I’ve encountered a strange behavior with ssl bufferevents:

1. My program calls bufferevent_write(),

2. (Some error occurs – which is ok) bufferevent_write calls my event_cb.

3. My event_cb releases the bufferevent.

4. Program segfaults.

I’ve worked with Valgrind and checked the libevent source code – it seems that after bufferevent_write is calling my event_cb (which releases the bufferevent) it then modifies a value in the ssl_bufferevent (which is already released).

So what’s the deal? Is it allowed to release a bufferevent with in its own events? Or is it not allowed?

As a workaround I should never release bufferevents within their events. Although it would be less efficient (I’ll have to execute an event to release the bufferevent).

Suggestions?

Thanks,

Tomer.