Fix dwarf.c build with GCC 10

Silcence a compile time warning message building the binutils with
gcc-10.

	* dwarf.c (display_debug_lines_decoded): Force a NUL termination
	of the truncated file name.

(cherry picked from commit e1104d08fe2fbfabcfa98aa00525211e47548bd8)

diff --git a/binutils/ChangeLog b/binutils/ChangeLog
index 24b0515fd68548828d8dfdf5665ab364299b0c45..fadd317151dc79b5e7c0e8f1cf5f844d9bb6a4d7 100644 (file)
--- a/binutils/ChangeLog
+++ b/binutils/ChangeLog
@@ -1,3 +1,8 @@
+2020-03-24  Nick Clifton  <nickc@redhat.com>
+
+       * dwarf.c (display_debug_lines_decoded): Force a NUL termination
+       of the truncated file name.
+
 2020-02-25  H.J. Lu  <hongjiu.lu@intel.com>
 
        PR binutils/25584

diff --git a/binutils/dwarf.c b/binutils/dwarf.c
index 35842f74b2ed2b34002553e7bf505f88ea3a49f3..6ecfab5d5a797a7ae8af19b6295b67ae628508dd 100644 (file)
--- a/binutils/dwarf.c
+++ b/binutils/dwarf.c
@@ -4905,6 +4905,11 @@ display_debug_lines_decoded (struct dwarf_section *  section,
                  strncpy (newFileName,
                           fileName + fileNameLength - MAX_FILENAME_LENGTH,
                           MAX_FILENAME_LENGTH + 1);
+                 /* FIXME: This is to pacify gcc-10 which can warn that the
+                    strncpy above might leave a non-NUL terminated string
+                    in newFileName.  It won't, but gcc's analysis doesn't
+                    quite go far enough to discover this.  */
+                 newFileName[MAX_FILENAME_LENGTH] = 0;
                }
              else
                {