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

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