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

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