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

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