summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authordgp <dgp@users.sourceforge.net>2014-11-01 14:52:55 (GMT)
committerdgp <dgp@users.sourceforge.net>2014-11-01 14:52:55 (GMT)
commit9d91e28e770e770f99f3c3115ab9e86e9d481a2d (patch)
tree7d4ddb7c507030ba39fa5a765f30a5dea7036c62
parenta4303c31209825c3819a237502f646868c4bc37d (diff)
downloadtcl-9d91e28e770e770f99f3c3115ab9e86e9d481a2d.zip
tcl-9d91e28e770e770f99f3c3115ab9e86e9d481a2d.tar.gz
tcl-9d91e28e770e770f99f3c3115ab9e86e9d481a2d.tar.bz2
Disable assertion until tls bug it detects is fixed.
-rw-r--r--generic/tclIO.c8
1 files changed, 7 insertions, 1 deletions
diff --git a/generic/tclIO.c b/generic/tclIO.c
index 207ce19..9cbc72c 100644
--- a/generic/tclIO.c
+++ b/generic/tclIO.c
@@ -2811,9 +2811,15 @@ FlushChannel(
* write in this call, and we've completed the BG flush.
* These are the two cases above. If we get here, that means
* there is some kind failure in the writable event machinery.
- */
+ *
+ * The tls extension indeed suffers from flaws in its channel
+ * event mgmt. See http://core.tcl.tk/tcl/info/c31ca233ca.
+ * Until that patch is broadly distributed, disable the
+ * assertion checking here, so that programs using Tcl and
+ * tls can be debugged.
assert(!calledFromAsyncFlush);
+ */
}
}