print_file_contents: allocate enough to include \0

related to #331
Previously, if max_chars was read, the null byte would be written
past the end of buf.

2 files changed, 7 insertions, 1 deletions

diff --git a/testcases/025-file-contents/expected_output.txt b/testcases/025-file-contents/expected_output.txt
index 5c56020..b3fb8e5 100644
--- a/testcases/025-file-contents/expected_output.txt
+++ b/testcases/025-file-contents/expected_output.txt
@@ -1 +1 @@
-contents | NONEXISTANT - 2: No such file or directory
+contents | con | NONEXISTANT - 2: No such file or directory
diff --git a/testcases/025-file-contents/i3status.conf b/testcases/025-file-contents/i3status.conf
index 26646cd..78f9f50 100644
--- a/testcases/025-file-contents/i3status.conf
+++ b/testcases/025-file-contents/i3status.conf
@@ -3,12 +3,18 @@ general {
 }
 
 order += "read_file EXISTING"
+order += "read_file TRUNCATED"
 order += "read_file NONEXISTANT"
 
 read_file EXISTING {
         path = "testcases/025-file-contents/short.txt"
 }
 
+read_file TRUNCATED {
+        path = "testcases/025-file-contents/short.txt"
+        max_characters = 3
+}
+
 read_file NONEXISTANT {
         path = "testcases/025-file-contents/nonexistant"
 }