RE: [Libevent-users] epoll erros

> The first thing to do here is to use event_enable_debug_mode() to have > libevent track event adds/deletes/etc to make sure that there's > nothing screwy going on there. > Here is the chain of events I was able to identify - An event for fd 14 is created - At some later point, my code deletes th

RE: [Libevent-users] epoll erros

> The first thing to do here is to use event_enable_debug_mode() to have > libevent track event adds/deletes/etc to make sure that there's > nothing screwy going on there. > Beside calling event_enable_debug_mode I understand I have to turn on debugging. How would I do that ? configure --enable-

Re: [Libevent-users] Re: help with debugging

On Fri, Sep 17, 2010 at 5:22 AM, Mihai Draghicioiu wrote: [...] > Core was generated by `/home/mihai/frogmod-justice/frogserv'. > Program terminated with signal 11, Segmentation fault. > [New process 14829] > #0  evhttp_request_get_input_buffer (req=0x99d90f8) at http.c:3014 > 3014    { > (gdb) up

Re: [Libevent-users] epoll erros

On Thu, Sep 16, 2010 at 2:59 PM, Gilad Benjamini wrote: > My Linux code, which uses libevent 2.0.x occasionally prints these error > messages >    Epoll ADD on fd 14 failed.  Old events were 0; read change was 1 (add); > write change was 0 (none).: File exists > When they appear, it can be as freq

[Libevent-users] Re: help with debugging

The crash seems to happen approximately daily. Here's more debugging text. mi...@evo:~/frogmod-justice$ gdb frogserv core.14829 GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: