summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorArtyom V. Poptsov <poptsov.artyom@gmail.com>2017-05-21 20:45:20 +0300
committerArtyom V. Poptsov <poptsov.artyom@gmail.com>2017-05-21 20:45:20 +0300
commitcb6dc775411ac12617a620fa77e763fe0fc0828e (patch)
treef2e0f32472beab8114ae3933371dbfbe6c3431b1 /NEWS
parentlog.c (_gssh_log_warning): New procedure (diff)
downloadguile-ssh-cb6dc775411ac12617a620fa77e763fe0fc0828e.tar.gz
channel-type.c (print_channel): Bugfix: Handle freed channels
Guile-SSH would always crash with SIGSEGV errors when tried to print a freed channel object (e.g. after calling 'close' on a channel). This patch fixes the bug. * libguile-ssh/channel-type.c (print_channel): Bugfix: Handle freed channels properly. * tests/client-server.scm ("channel-request-exec, printing a freed channel"): New test case. * NEWS: Update.
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS10
1 files changed, 9 insertions, 1 deletions
diff --git a/NEWS b/NEWS
index 50b2275..397c653 100644
--- a/NEWS
+++ b/NEWS
@@ -13,7 +13,15 @@ Copyright (C) Artyom V. Poptsov <poptsov.artyom@gmail.com>
**** 'node-guile-version' now does not fail
The procedure would always fail to get Guile version. Now that should be
fixed.
-** Update uit tests
+*** In (ssh channel)
+**** Printing a freed channel doesn't lead to SIGSEGV anymore
+ Guile-SSH would always crash with SIGSEGV errors when tried to print a
+ freed channel object (e.g. after calling 'close' on a channel). This bug
+ is fixed now by introducing new checks.
+
+ Now a freed channel will be printed like this:
+ #<unknown channel (freed) 9412f0>
+** Update unit tests
*** Add test cases for fixed bugs
* Changes in version 0.11.1 (2017-05-09)