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

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