[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [Libevent-users] deadlock in version 2.0.5

To: libevent-users@xxxxxxxxxxxxx
Subject: Re: [Libevent-users] deadlock in version 2.0.5
From: Nick Mathewson <nickm@xxxxxxxxxxxxx>
Date: Fri, 13 Aug 2010 13:17:51 -0400
Delivered-to: archiver@xxxxxxxx
Delivered-to: libevent-users-outgoing@xxxxxxxx
Delivered-to: libevent-users@xxxxxxxx
Delivery-date: Fri, 13 Aug 2010 13:18:03 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; bh=iNyxw80zbK+9qoRCsyZORpnOg+OVR1vOuzp38yVPg/g=; b=qgegpw2ugGgRUdWg2kETjYC9lABPfBgl+F7NlGV/GZ9YxxMVs9Y53pGCmsVRJQpUp2 +IQPyetz9+D9/DxmzQ1MCJBq5LL042HXH9H42FEU3GSKRRetFiyEXLG2zrjhgSNpSdCi TyZK9fTLR2Xg4gllBy2cuDwcHjPDWGRP3/9w4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=dshegu74E0HckLeK36K9DtJKaeT1yJgaW/qdpdKQQVz9Llj6sdwncz2wI20cPyhwe0 L0Ab8MywGWV0/ZVeuLpTaNLwJEv4VVRcHr7K94ADAwAZKC079vjKEfUbRJ9fKvaQhSWW V23ypMCH1X2apnUw2XOw3nHH1JC26wcYuBRi8=
In-reply-to: <6CB5C4A9FCDB4F4283D69D65B8B4ABA8029C88C256@xxxxxxxxxxxxxxxxxxxx>
References: <AQHLOef81B9Zkh9La0Gy0SXfr4nL0g==> <6CB5C4A9FCDB4F4283D69D65B8B4ABA8029C88C256@xxxxxxxxxxxxxxxxxxxx>
Reply-to: libevent-users@xxxxxxxxxxxxx
Sender: owner-libevent-users@xxxxxxxxxxxxx

On Thu, Aug 12, 2010 at 2:31 AM, Avi Bab <ABab@xxxxxxxxxxxxx> wrote:
> The scenario –

Ick.  I've added this one to the bugtracker as
https://sourceforge.net/tracker/index.php?func=detail&aid=3044479&group_id=50884&atid=461322
; further discussion there.

From what I can see now, there doesn't seem to be a better solution
than moving current_event_lock from being a lock to being a condition
or something.  More thought is probably needed, though. :/

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

Follow-Ups:
- Re: [Libevent-users] deadlock in version 2.0.5
  - From: Nick Mathewson

References:
- [Libevent-users] deadlock in version 2.0.5
  - From: Avi Bab

Prev by Author: Re: [Libevent-users] Compiling libevent on Windows
Next by Author: Re: [Libevent-users] Ability to shutdown() socket with bufferevents?
Previous by thread: [Libevent-users] deadlock in version 2.0.5
Next by thread: Re: [Libevent-users] deadlock in version 2.0.5
Index(es):
- Author
- Thread