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

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