|
 |
405ea9 |
From FEDORA_PATCHES Mon Sep 17 00:00:00 2001
|
|
|
405ea9 |
From: Fedora GDB patches <invalid@email.com>
|
|
|
405ea9 |
Date: Fri, 27 Oct 2017 21:07:50 +0200
|
|
|
405ea9 |
Subject: gdb-6.5-last-address-space-byte-test.patch
|
|
|
405ea9 |
|
|
|
405ea9 |
;; Testcase for deadlocking on last address space byte; for corrupted backtraces.
|
|
|
405ea9 |
;;=fedoratest
|
|
|
405ea9 |
|
|
|
405ea9 |
diff --git a/gdb/testsuite/gdb.base/largecore-last-address-lock.exp b/gdb/testsuite/gdb.base/largecore-last-address-lock.exp
|
|
|
405ea9 |
new file mode 100644
|
|
|
405ea9 |
--- /dev/null
|
|
|
405ea9 |
+++ b/gdb/testsuite/gdb.base/largecore-last-address-lock.exp
|
|
|
405ea9 |
@@ -0,0 +1,49 @@
|
|
|
405ea9 |
+# Copyright 2006 Free Software Foundation, Inc.
|
|
|
405ea9 |
+
|
|
|
405ea9 |
+# This program is free software; you can redistribute it and/or modify
|
|
|
405ea9 |
+# it under the terms of the GNU General Public License as published by
|
|
|
405ea9 |
+# the Free Software Foundation; either version 2 of the License, or
|
|
|
405ea9 |
+# (at your option) any later version.
|
|
|
405ea9 |
+#
|
|
|
405ea9 |
+# This program is distributed in the hope that it will be useful,
|
|
|
405ea9 |
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
405ea9 |
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
405ea9 |
+# GNU General Public License for more details.
|
|
|
405ea9 |
+#
|
|
|
405ea9 |
+# You should have received a copy of the GNU General Public License
|
|
|
405ea9 |
+# along with this program; if not, write to the Free Software
|
|
|
405ea9 |
+# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
|
|
|
405ea9 |
+
|
|
|
405ea9 |
+if $tracelevel then {
|
|
|
405ea9 |
+ strace $tracelevel
|
|
|
405ea9 |
+}
|
|
|
405ea9 |
+
|
|
|
405ea9 |
+# Get things started.
|
|
|
405ea9 |
+
|
|
|
405ea9 |
+gdb_exit
|
|
|
405ea9 |
+gdb_start
|
|
|
405ea9 |
+
|
|
|
405ea9 |
+# i386 (32-bit) only: gdb with Red Hat largecore patch did lock up:
|
|
|
405ea9 |
+# https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=103263
|
|
|
405ea9 |
+# https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=210614
|
|
|
405ea9 |
+
|
|
|
405ea9 |
+# i386: Bug exists when the `target_xfer_memory' condition
|
|
|
405ea9 |
+# `(memaddr + len < region->hi)' operates on 64-bit operands on
|
|
|
405ea9 |
+# largecore-patched with 32-bit addresses and so it can get `false' with
|
|
|
405ea9 |
+# arbitrary `len'.
|
|
|
405ea9 |
+
|
|
|
405ea9 |
+# x86_64: The bug is not present as the operands and calculations have the same
|
|
|
405ea9 |
+# bit size. Would would still need to pass there the highest address
|
|
|
405ea9 |
+# (`memaddr == 0xffffffffffffffff') but we would need to pass `len == 0'
|
|
|
405ea9 |
+# to make the condition `(memaddr + len < region->hi)' false.
|
|
|
405ea9 |
+# `len == 0' would get caught eariler.
|
|
|
405ea9 |
+
|
|
|
405ea9 |
+# Error in the success case is immediate.
|
|
|
405ea9 |
+set timeoutold ${timeout}
|
|
|
405ea9 |
+set timeout 10
|
|
|
405ea9 |
+
|
|
|
405ea9 |
+gdb_test "x/xb 0xffffffff" \
|
|
|
405ea9 |
+ "Cannot access memory at address 0xffffffff" \
|
|
|
405ea9 |
+ "Read the last address space byte"
|
|
|
405ea9 |
+
|
|
|
405ea9 |
+set timeout ${timeoutold}
|