Re: [Libevent-users] libevent with python segfaulting

[Nick Mathewson <nickm@xxxxxxxxxxxxx>]

On Sun, Aug 1, 2010 at 3:01 PM, Michael Gale <gale.michael@xxxxxxxxx> wrote:
> Hello,
>     I am using the latest release of libevent-python and the latest release
> of libevent-1.4.
> After I am done writing data and close the socket I attempt to remove the
> write event callback from the event loop. If I do this the server segfaults
> between 500 and 600 connections.
> If I do not attempt to remove the write event for the fd, the server appears
> to scale with out issues accept the connection objects are never garbaged
> collected and it eventually runs out of memory.
> Any suggestions on how to resolve / find the segfault issue or a better
> method to use libevent with python?

So, if you can attach a debugger and get a stack trace, or run in a
debugger and get a stack trace, or get a core file and use it to
generate a stack trace, that's the usual way to debug segfault issues.

You could also try coming up with a minimal program that demonstrates
this, then show it to others and see if they can spot the problem.

You might also try contacting the libevent-python maintainers; I don't
know if they're on this list, but debugging libevent-and-python issues
is likely more their expertise.

-- 
Nick
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users    in the body.