Blame SOURCES/gdb-6.6-buildid-locate-misleading-warning-missing-debuginfo-rhbz981154.patch

79b363
From FEDORA_PATCHES Mon Sep 17 00:00:00 2001
79b363
From: Fedora GDB patches <invalid@email.com>
79b363
Date: Fri, 27 Oct 2017 21:07:50 +0200
79b363
Subject: 
79b363
 gdb-6.6-buildid-locate-misleading-warning-missing-debuginfo-rhbz981154.patch
79b363
79b363
;; Fix 'gdb gives highly misleading error when debuginfo pkg is present,
79b363
;; but not corresponding binary pkg' (RH BZ 981154).
79b363
;;=push+jan
79b363
79b363
Comments by Sergio Durigan Junior <sergiodj@redhat.com>:
79b363
79b363
  This is the fix for RH BZ #981154
79b363
79b363
  It is mainly a testcase addition, but a minor fix in the gdb/build-id.c
79b363
  file was also needed.
79b363
79b363
  gdb/build-id.c was added by:
79b363
79b363
  commit dc294be54c96414035eed7d53dafdea0a6f31a72
79b363
  Author: Tom Tromey <tromey@redhat.com>
79b363
  Date:   Tue Oct 8 19:56:15 2013 +0000
79b363
79b363
  and had a little thinko there.  The variable 'filename' needs to be set to
79b363
  NULL after it is free'd, otherwise the code below thinks that it is still
79b363
  valid and doesn't print the necessary warning ("Try: yum install ...").
79b363
79b363
diff --git a/gdb/testsuite/gdb.base/rhbz981154-misleading-yum-install-warning.exp b/gdb/testsuite/gdb.base/rhbz981154-misleading-yum-install-warning.exp
79b363
new file mode 100644
79b363
--- /dev/null
79b363
+++ b/gdb/testsuite/gdb.base/rhbz981154-misleading-yum-install-warning.exp
79b363
@@ -0,0 +1,97 @@
79b363
+#   Copyright (C) 2014  Free Software Foundation, Inc.
79b363
+
79b363
+# This program is free software; you can redistribute it and/or modify
79b363
+# it under the terms of the GNU General Public License as published by
79b363
+# the Free Software Foundation; either version 3 of the License, or
79b363
+# (at your option) any later version.
79b363
+#
79b363
+# This program is distributed in the hope that it will be useful,
79b363
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
79b363
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
79b363
+# GNU General Public License for more details.
79b363
+#
79b363
+# You should have received a copy of the GNU General Public License
79b363
+# along with this program.  If not, see <http://www.gnu.org/licenses/>.
79b363
+
79b363
+standard_testfile "normal.c"
79b363
+
79b363
+if { [prepare_for_testing ${testfile}.exp ${testfile} ${srcfile}] } {
79b363
+    return -1
79b363
+}
79b363
+
79b363
+# Get the build-id of the file
79b363
+set build_id_debug_file [build_id_debug_filename_get $binfile]
79b363
+regsub -all ".debug$" $build_id_debug_file "" build_id_without_debug
79b363
+
79b363
+# Run to main
79b363
+if { ![runto_main] } {
79b363
+    return -1
79b363
+}
79b363
+
79b363
+# We first need to generate a corefile
79b363
+set escapedfilename [string_to_regexp [standard_output_file gcore.test]]
79b363
+set core_supported 0
79b363
+gdb_test_multiple "gcore [standard_output_file gcore.test]" \
79b363
+	"save a corefile" \
79b363
+{
79b363
+  -re "Saved corefile ${escapedfilename}\[\r\n\]+$gdb_prompt $" {
79b363
+    pass "save a corefile"
79b363
+    global core_supported
79b363
+    set core_supported 1
79b363
+  }
79b363
+  -re "Can't create a corefile\[\r\n\]+$gdb_prompt $" {
79b363
+    unsupported "save a corefile"
79b363
+    global core_supported
79b363
+    set core_supported 0
79b363
+  }
79b363
+}
79b363
+
79b363
+if {!$core_supported} {
79b363
+  return -1
79b363
+}
79b363
+
79b363
+# Move the binfile to a temporary name
79b363
+remote_exec build "mv $binfile ${binfile}.old"
79b363
+
79b363
+# Reinitialize GDB and see if we get a yum/dnf warning
79b363
+gdb_exit
79b363
+gdb_start
79b363
+gdb_reinitialize_dir $srcdir/$subdir
79b363
+
79b363
+with_test_prefix "first run:" {
79b363
+    gdb_test "set build-id-verbose 1" "" \
79b363
+	"set build-id-verbose"
79b363
+
79b363
+    gdb_test "set debug-file-directory [file dirname [standard_output_file gcore.test]]" "" \
79b363
+	"set debug-file-directory"
79b363
+
79b363
+    gdb_test "core-file [standard_output_file gcore.test]" \
79b363
+	"Missing separate debuginfo for the main executable file\r\nTry: (yum|dnf) --enablerepo='\\*debug\\*' install [standard_output_file $build_id_without_debug]\r\n.*" \
79b363
+	"test first yum/dnf warning"
79b363
+}
79b363
+
79b363
+# Now we define and create our .build-id
79b363
+file mkdir [file dirname [standard_output_file ${build_id_without_debug}]]
79b363
+# Cannot use "file link" (from TCL) because it requires the target file to
79b363
+# exist.
79b363
+remote_exec build "ln -s $binfile [standard_output_file ${build_id_without_debug}]"
79b363
+
79b363
+# Reinitialize GDB to get the second yum/dnf warning
79b363
+gdb_exit
79b363
+gdb_start
79b363
+gdb_reinitialize_dir $srcdir/$subdir
79b363
+
79b363
+with_test_prefix "second run:" {
79b363
+    gdb_test "set build-id-verbose 1" "" \
79b363
+	"set build-id-verbose"
79b363
+
79b363
+    gdb_test "set debug-file-directory [file dirname [standard_output_file gcore.test]]" "" \
79b363
+	"set debug-file-directory"
79b363
+
79b363
+    gdb_test "core-file [standard_output_file gcore.test]" \
79b363
+	"Missing separate debuginfo for the main executable file\r\nTry: (yum|dnf) --enablerepo='\\*debug\\*' install $binfile\r\n.*" \
79b363
+	"test second yum/dnf warning"
79b363
+}
79b363
+
79b363
+# Leaving the link there will cause breakage in the next run.
79b363
+remote_exec build "rm -f [standard_output_file ${build_id_without_debug}]"