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

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