On Tue, Dec 21, 2010 at 10:57 AM, Mark Ellzey wrote:
> On Mon, Dec 20, 2010 at 01:32:50AM -0500, Kevin Bowling wrote:
> > I'm at wit's end with a libevent threading bug. As part of a disconnect
> > client routine, I manually call the errorcb with EVENT_ERROR_EOF. The
> idea
> > was to keep all
On Mon, Dec 20, 2010 at 01:32:50AM -0500, Kevin Bowling wrote:
> I'm at wit's end with a libevent threading bug. As part of a disconnect
> client routine, I manually call the errorcb with EVENT_ERROR_EOF. The idea
> was to keep all the cleanup code in one callback but I'm beginning to think
> thi
I'm at wit's end with a libevent threading bug. As part of a disconnect
client routine, I manually call the errorcb with EVENT_ERROR_EOF. The idea
was to keep all the cleanup code in one callback but I'm beginning to think
this was ill-conceived. Somehow, libevent is entering a condition wait an
