Clarify that no new requests may be added to a resolver channel that is
currently being destroyed.
---
ares_destroy.3 |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/ares_destroy.3 b/ares_destroy.3
index 79171ec..3724df1 100644
--- a/ares_destroy.3
+++ b/ares_destroy.3
@@
This commit clarifies the behaviour of ares_cancel() with respect to
callbacks and adds missing documentation of ARES_ECANCELLED to the man
pages of the affected functions.
---
ares_cancel.3|4 +++-
ares_gethostbyaddr.3 |3 +++
ares_gethostbyname.3 |3 +++
ares_getnameinfo.3
An invocation of ares_cancel() walks through the request list, calling
the callbacks of all pending requests on a channel. Previously, if such
a callback added a new request to the channel, the request list might
not end up empty, causing an abort by assertion failure. The present
commit ensures
On Mon, 8 Apr 2013, Alexander Klauer wrote:
An invocation of ares_cancel() walks through the request list, calling
the callbacks of all pending requests on a channel.
Thanks a lot. Your mini-series has been merged and pushed!
--
/ daniel.haxx.se