Hi Nick
Well my problems are gone, but only because I changed the design.
Initially I was using a very inefficient method, whereby I would create a
non persistent event every time I wanted to write some data to a socket
(event_new followed by event_add). In the callback, if all the data was sent
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 doing
> anything wrong, and why the code would work for s
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 doing
anything wrong, and why the code would work for some time then go crazy.
Thanks
Sherif
On Sun, Apr 10, 2011
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 Dispatching send event base
10/04/11 11:27:09 1425 3068124016 Starting loop for base 0x8808ad0
10
Sorry about the late reply.
I'm not very good with gdb. Actually I'm just a beginner with gdb.
To generate the above trace I first waited for a deadlock to occur. I then
killed the process using "kill -6 " to force the process to dump core.
I then opened the core file using gdb and ran the comman
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.c
> which is the opening brace of the function.
> How would I walk through ctx->eve
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.c
which is the opening brace of the function.
How would I walk through ctx->events?
Thanks
Sherif
On Fri, Apr 8, 2011 at 9:38 PM, Nick Mat
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 so.
> The deadlock occurs with the event base responsible for sending network
> packets
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
