Fix up safe_strerror constification

The earlier patch to constify safe_strerror missed a couple of spots,
corrected here.

gdb/ChangeLog
2019-11-01  Tom Tromey  <tromey@adacore.com>

	* gdbsupport/mingw-strerror.c (safe_strerror): Constify result.

Change-Id: I36d5ced144d27b1a6734d9ab9a10a7b9f339ae88

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 4231ac11fe6348cbc264570ed470a726ff2b2571..500c4868c8f44a37c3700afce54f9b629e1cac4f 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2019-11-01  Tom Tromey  <tromey@adacore.com>
+
+       * gdbsupport/mingw-strerror.c (safe_strerror): Constify result.
+
 2019-11-01  Christian Biesinger  <cbiesinger@google.com>
 
        * configure: Regenerate.

diff --git a/gdb/gdbsupport/mingw-strerror.c b/gdb/gdbsupport/mingw-strerror.c
index 6386330062cbffb46901e7f7b7d35e796d9b7658..893b7ca1779e4d8d2f94ed5d94d28cc486b6185e 100644 (file)
--- a/gdb/gdbsupport/mingw-strerror.c
+++ b/gdb/gdbsupport/mingw-strerror.c
@@ -28,7 +28,7 @@
    unfortunately this includes all socket-related error codes.
    This replacement tries to find a system-provided error message.  */
 
-char *
+const char *
 safe_strerror (int errnum)
 {
   static char *buffer;