Check result of "write"

Some distros enable _FORTIFY_SOURCE by default, which caught a failure
to check the result of "write" in scoped_mmap-selftests.c.  This patch
fixes the problem.

ChangeLog
2018-08-08  Tom Tromey  <tom@tromey.com>

	* unittests/scoped_mmap-selftests.c: Check result of "write".

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index b534e95450bf1a8b30bde577d82b4e19f1eb6b23..49a7e396ccf076cb4d07f4b5dd479fb73b3ac456 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2018-08-08  Tom Tromey  <tom@tromey.com>
+
+       * unittests/scoped_mmap-selftests.c: Check result of "write".
+
 2018-08-08  Jim Wilson  <jimw@sifive.com>
 
        * riscv-tdep.c (enum opcode): Add jump, branch, lr, and sc opcodes.

diff --git a/gdb/unittests/scoped_mmap-selftests.c b/gdb/unittests/scoped_mmap-selftests.c
index d70a56a1862d5b35d0f7cd11071a0c139c2d129a..e9d4afdffc5b91330cd2f92d3f906b4d31f4d101 100644 (file)
--- a/gdb/unittests/scoped_mmap-selftests.c
+++ b/gdb/unittests/scoped_mmap-selftests.c
@@ -91,7 +91,7 @@ test_normal ()
   int fd = mkstemp (filename);
   SELF_CHECK (fd >= 0);
 
-  write (fd, "Hello!", 7);
+  SELF_CHECK (write (fd, "Hello!", 7) == 7);
   close (fd);
 
   gdb::unlinker unlink_test_file (filename);