[Libevent-users] Assertion error + Segmentation Fault

2010-04-08 Thread Sherif Fanous
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

Re: [Libevent-users] Assertion error + Segmentation Fault

2010-04-08 Thread Sherif Fanous
gt; 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. > >

Re: [Libevent-users] Assertion error + Segmentation Fault

2010-05-18 Thread Sherif Fanous
Thanks for your support I solved my problems a while ago, and I completely redesigned the code because as you said it was running in O(N) Thanks for your support mate Cheers On Mon, May 17, 2010 at 11:57 PM, Nick Mathewson wrote: > On Thu, Apr 8, 2010 at 7:46 AM, Sherif Fanous >

[Libevent-users] libevent with EV_WRITE question

2010-05-29 Thread Sherif Fanous
Hi I have the following scenario, and want to verify the expected outcome pthread_wrlock_rdlock(&(server->lock)); if (server->is_connected) { struct send_packets_args *send_packets_args; send_packets_args = malloc(sizeof (struct send_packets_args)); // Initialize send_packets_args to

Re: [Libevent-users] libevent with EV_WRITE question

2010-06-03 Thread Sherif Fanous
Thank you for an excellent explanation Cheers On Thu, Jun 3, 2010 at 4:26 PM, Nick Mathewson wrote: > On Sat, May 29, 2010 at 6:44 AM, Sherif Fanous > wrote: > > Hi > > I have the following scenario, and want to verify the expected outcome > > pthread_wrlock_rdlock(

[Libevent-users] Threading question in libevent

2010-11-20 Thread Sherif Fanous
Hello I have my event callback receiving data from the network using recv. If recv returns 0 (FIN received), I call a function to disconnect and cleanup. Part of my cleanup is as follows if (server->receive_event) { event_free(server->receive_event); server->receive_event = NULL; } I h

Re: [Libevent-users] Threading question in libevent

2010-11-21 Thread Sherif Fanous
Yes, I figured it out by delving into the libevent source code yesterday I have removed the above stub from the locked code, so now the callback always completes, and the issue is solved. Thanks On Sun, Nov 21, 2010 at 9:58 PM, Nick Mathewson wrote: > On Sat, Nov 20, 2010 at 6:21 AM, She

Re: [Libevent-users] ANN: Libevent 2.0.9-rc is released

2010-11-30 Thread Sherif Fanous
The Changelog states the following Disable changelist for epoll by default because of Linux dup() bug; add an option and/or an envvar to reenable it for speed. Can an example be provided on how to enable it please Thanks On Tue, Nov 30, 2010 at 4:46 PM, Ralph Castain wrote: > And I have a Win

Re: [Libevent-users] ANN: Libevent 2.0.9-rc is released

2010-11-30 Thread Sherif Fanous
Thanks a lot On Tue, Nov 30, 2010 at 5:31 PM, Frank Denis wrote: > Le Tue, Nov 30, 2010 at 05:02:22PM +0200, Sherif Fanous ecrivait : > > The Changelog states the following > > > > Disable changelist for epoll by default because of Linux dup() bug; add > an > &

[Libevent-users] Event never triggering

2011-02-28 Thread Sherif Fanous
Hi I'm facing some unusual behaviour, that I'm unable to debug This is the code I'm facing trouble with while (!do_terminate) { struct instruction_queue_node *send_queue_node; send_queue_node = (struct instruction_queue_node *) dequeue(send_outgoing_packets_queue); i

[Libevent-users] Deadlock driving me nuts

2011-04-08 Thread Sherif Fanous
Hello I'm running into a deadlock using libevent. I've been trying to figure out why or where it is happening for the last 3 days but have failed to do so. The deadlock occurs with the event base responsible for sending network packets. Below is a gdb output showing the deadlocked threads. Thread

Re: [Libevent-users] Deadlock driving me nuts

2011-04-09 Thread Sherif Fanous
PM, Nick Mathewson wrote: > On Fri, Apr 8, 2011 at 3:37 AM, Sherif Fanous > wrote: > > Hello > > I'm running into a deadlock using libevent. I've been trying to figure > out > > why or where it is happening for the last 3 days but have failed to do >

Re: [Libevent-users] Deadlock driving me nuts

2011-04-10 Thread Sherif Fanous
9, 2011 at 2:58 PM, Nick Mathewson wrote: > On Sat, Apr 9, 2011 at 4:16 AM, Sherif Fanous > wrote: > > As a matter of fact, the thread in question is usually stuck in > > event_active_nolock. > > The funny thing is that it shows that it's stuck in line 2212 in event.

Re: [Libevent-users] Deadlock driving me nuts

2011-04-10 Thread Sherif Fanous
10/04/11 11:27:09 1425 3068124016 base: 0x8808ad0, ev: 0xb13f00f8 10/04/11 11:27:09 1425 3068124016 base: 0x8808ad0, ev: 0xb13f00f8 The last line repeats to infinity. On Sun, Apr 10, 2011 at 11:00 AM, Sherif Fanous wrote: > Sorry about the late reply. > > I'm not very good with gdb

Re: [Libevent-users] Deadlock driving me nuts

2011-04-10 Thread Sherif Fanous
On Sun, Apr 10, 2011 at 11:56 AM, Sherif Fanous wrote: > Ok I managed to get some more info > > It deadlocked and this is what I got in my log file > > 10/04/11 11:27:09 1466 3035069296 1 events are added to the send event > base > 10/04/11 11:27:09 1425 3068124016 Dispat

Re: [Libevent-users] Deadlock driving me nuts

2011-04-12 Thread Sherif Fanous
> On Sun, Apr 10, 2011 at 2:55 PM, Sherif Fanous > wrote: > > I'm willing to post code snippets if it helps. > > What I'm seeing is that after some time adding just 1 event causes an > > infinite loop in evmap_io_active, and I can't figure out if I'm doi