On 23 September 2012 07:50, Vadym S. Khondar <v.khon...@invisilabs.com> wrote:
> (The task is: after certain point need to give up on bufferevent without any > callbacks invoked as they might be called with already freed structs as > cbarg). The oft-overlooked problem with threaded code is that you can't guarantee you can cancel something else in another thread. So sure, if the bufferevent isn't in-flight in another thread, you can cancel it. But you have to be prepared for the cancellation to fail because it's already involved in an IO. Just putting it out there, Adrian *********************************************************************** To unsubscribe, send an e-mail to majord...@freehaven.net with unsubscribe libevent-users in the body.