Blame SOURCES/gdb-rhbz1842691-corefile-mem-access-11of15.patch

46818e
From FEDORA_PATCHES Mon Sep 17 00:00:00 2001
46818e
From: Keith Seitz <keiths@redhat.com>
46818e
Date: Tue, 28 Jul 2020 09:26:44 -0400
46818e
Subject: gdb-rhbz1842691-corefile-mem-access-11of15.patch
46818e
46818e
;; Adjust coredump-filter.exp to account for NT_FILE note handling
46818e
;; Kevin Buettner, RH BZ 1842961
46818e
46818e
   Author: Kevin Buettner <kevinb@redhat.com>
46818e
   Date:   Fri Jul 3 20:10:22 2020 -0700
46818e
46818e
    Adjust coredump-filter.exp to account for NT_FILE note handling
46818e
46818e
    This commit makes adjustments to coredump-filter.exp to account
46818e
    for the fact that NT_FILE file-backed mappings are now available
46818e
    when a core file is loaded.  Thus, a test which was expected
46818e
    to PASS when a memory region was determined to be unavailable
46818e
    (due to no file-backed mappings being available) will now FAIL
46818e
    due to those mappings being available from having loaded the
46818e
    NT_FILE note.
46818e
46818e
    I had originally marked the test as XFAIL, but Mihails Strasuns
46818e
    suggested a much better approach:
46818e
46818e
        1) First test that it still works if file is accessible in the
46818e
           filesystem.
46818e
        2) Temporarily move / rename the file and test that disassembly
46818e
           doesn't work anymore.
46818e
46818e
    That's what this commit implements.
46818e
46818e
    gdb/testsuite/ChangeLog:
46818e
46818e
    	* gdb.base/coredump-filter.exp: Add second
46818e
    	non-Private-Shared-Anon-File test.
46818e
    	(test_disasm): Rename binfile for test which is expected
46818e
    	to fail.
46818e
46818e
diff --git a/gdb/testsuite/gdb.base/coredump-filter.exp b/gdb/testsuite/gdb.base/coredump-filter.exp
46818e
--- a/gdb/testsuite/gdb.base/coredump-filter.exp
46818e
+++ b/gdb/testsuite/gdb.base/coredump-filter.exp
46818e
@@ -80,15 +80,26 @@ proc do_load_and_test_core { core var working_var working_value dump_excluded }
46818e
 # disassemble of a function (i.e., the binary's .text section).  GDB
46818e
 # should fail in this case.  However, it must succeed if the binary is
46818e
 # provided along with the corefile.  This is what we test here.
46818e
+#
46818e
+# A further complication is that Linux NT_FILE notes are now read from
46818e
+# the corefile.  This note allows GDB to find the binary for file
46818e
+# backed mappings even though the binary wasn't loaded by GDB in the
46818e
+# conventional manner.  In order to see the expected failure for this
46818e
+# case, we rename the binary in order to perform this test.
46818e
 
46818e
 proc test_disasm { core address should_fail } {
46818e
-    global testfile hex
46818e
+    global testfile hex binfile
46818e
 
46818e
     # Restart GDB without loading the binary.
46818e
     with_test_prefix "no binary" {
46818e
 	gdb_exit
46818e
 	gdb_start
46818e
 
46818e
+	set hide_binfile [standard_output_file "${testfile}.hide"]
46818e
+	if { $should_fail == 1 } {
46818e
+	    remote_exec host "mv -f $binfile $hide_binfile"
46818e
+	}
46818e
+
46818e
 	set core_loaded [gdb_core_cmd "$core" "load core"]
46818e
 	if { $core_loaded == -1 } {
46818e
 	    fail "loading $core"
46818e
@@ -96,6 +107,7 @@ proc test_disasm { core address should_fail } {
46818e
 	}
46818e
 
46818e
 	if { $should_fail == 1 } {
46818e
+	    remote_exec host "mv -f $hide_binfile $binfile"
46818e
 	    gdb_test "x/i \$pc" "=> $hex:\tCannot access memory at address $hex" \
46818e
 		"disassemble function with corefile and without a binary"
46818e
 	} else {
46818e
@@ -225,5 +237,9 @@ foreach item $all_anon_corefiles {
46818e
 }
46818e
 
46818e
 with_test_prefix "loading and testing corefile for non-Private-Shared-Anon-File" {
46818e
+    test_disasm $non_private_shared_anon_file_core $main_addr 0
46818e
+}
46818e
+
46818e
+with_test_prefix "loading and testing corefile for non-Private-Shared-Anon-File with renamed binary" {
46818e
     test_disasm $non_private_shared_anon_file_core $main_addr 1
46818e
 }