My apologies, I overlooked that,
Wouter
On 04/08/2010 02:02 PM, Sherif Fanous wrote:
> This lock is not for the event_base
>
> The events and event_base is only accessed from this thread.
>
> The lock is for the server object. I want to safely read the
> following server->is_socket_connected,
This lock is not for the event_base
The events and event_base is only accessed from this thread.
The lock is for the server object. I want to safely read the
following server->is_socket_connected, and server->socket_descriptor.
On Thu, Apr 8, 2010 at 1:52 PM, W.C.A. Wijngaards wrote:
> On 04/08
On 04/08/2010 01:46 PM, Sherif Fanous wrote:
> Can anyone please tell me what I'm doing wrong here? Is it an internal
> libevent problem, or is my code messing up somewhere?
> pthread_rwlock_rdlock(&(server->lock));
wrlock.
event_add modifies the event base.
Best regards,
Wouter
*
Hi
I am using libevent 2.0.4 alpha in my C application.
The below snapshot of my code occasionally encounters the following 2
problems
1. [err] event.c:1961: Assertion !(ev->ev_flags & ~EVLIST_ALL) failed in
event_del_internal
Aborted
2. Segmentation Fault. I've traced down that it
