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

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