From: Philip Withnall <philip.withnall@collabora.co.uk>
Date: Wed, 16 Apr 2014 18:03:56 +0000 (+0100)
Subject: gio: Document that GSocket is not thread safe
X-Git-Tag: 2.41.1~115
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=2b247e158991c9698c7cb53731395de2b69cb086;p=platform%2Fupstream%2Fglib.git

gio: Document that GSocket is not thread safe

https://bugzilla.gnome.org/show_bug.cgi?id=726318
---

diff --git a/gio/gsocket.c b/gio/gsocket.c
index 067431b..6713d0a 100644
--- a/gio/gsocket.c
+++ b/gio/gsocket.c
@@ -117,6 +117,10 @@
  * account the fact that your program will not automatically be killed
  * if it tries to write to %stdout after it has been closed.
  *
+ * Like most other APIs in GLib, #GSocket is not inherently thread safe. To use
+ * a #GSocket concurrently from multiple threads, you must implement your own
+ * locking.
+ *
  * Since: 2.22
  */