From: Luis Machado <lgustavo@codesourcery.com>
To: "'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: [PATCH] Harden gdb.base/bp-permanent.exp
Date: Thu, 09 Apr 2015 17:11:00 -0000 [thread overview]
Message-ID: <5526B296.8040000@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]
This testcase does not work as expected in QEMU (aarch64 QEMU in my
case). It fails when trying to manually write the breakpoint instruction
to a certain PC address.
(gdb) p /x addr_bp[0] = buffer[0]^M
Cannot access memory at address 0x400834^M
(gdb) PASS: gdb.base/bp-permanent.exp: always_inserted=off,
sw_watchpoint=0: setup: p /x addr_bp[0] = buffer[0]
p /x addr_bp[1] = buffer[1]^M
Cannot access memory at address 0x400835^M
(gdb) PASS: gdb.base/bp-permanent.exp: always_inserted=off,
sw_watchpoint=0: setup: p /x addr_bp[1] = buffer[1]
p /x addr_bp[2] = buffer[2]^M
Cannot access memory at address 0x400836^M
(gdb) PASS: gdb.base/bp-permanent.exp: always_inserted=off,
sw_watchpoint=0: setup: p /x addr_bp[2] = buffer[2]
p /x addr_bp[3] = buffer[3]^M
Cannot access memory at address 0x400837^M
(gdb) PASS: gdb.base/bp-permanent.exp: always_inserted=off,
sw_watchpoint=0: setup: p /x addr_bp[3] = buffer[3]
The following patch prevents a number of failures by detecting this and
bailing out in case the target has such a restriction. Writing to .text
from within the program isn't any better. It just leads to a SIGSEGV.
Before the patch:
=== gdb Summary ===
# of expected passes 66
# of unexpected failures 56
After the patch:
=== gdb Summary ===
# of expected passes 26
# of unsupported tests 4
I regtested this on x86-64 and it still works fine.
Ok?
[-- Attachment #2: bp-permanent.diff --]
[-- Type: text/x-patch, Size: 1043 bytes --]
2015-04-09 Luis Machado <lgustavo@codesourcery.com>
gdb/testsuite/
* gdb.base/bp-permanent.exp (test): Handle the case of being unable
to write to the .text section.
diff --git a/gdb/testsuite/gdb.base/bp-permanent.exp b/gdb/testsuite/gdb.base/bp-permanent.exp
index 81a5293..9193db8 100644
--- a/gdb/testsuite/gdb.base/bp-permanent.exp
+++ b/gdb/testsuite/gdb.base/bp-permanent.exp
@@ -104,7 +104,18 @@ proc test {always_inserted sw_watchpoint} {
# to memory manually.
set count [expr $address_after_bp - $address_bp]
for {set i 0} {$i < $count} {incr i} {
- gdb_test "p /x addr_bp\[$i\] = buffer\[$i\]" " = .*"
+ gdb_test_multiple "p /x addr_bp\[$i\] = buffer\[$i\]" $test {
+ -re "Cannot access memory at address $hex.*$gdb_prompt $" {
+ # Some targets (QEMU for one) do not allow writes to the
+ # .text section. It is no use continuing with the test
+ # at this point. Just return.
+ unsupported $test
+ return
+ }
+ -re " = .*$gdb_prompt $" {
+ pass $test
+ }
+ }
}
}
next reply other threads:[~2015-04-09 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 17:11 Luis Machado [this message]
2015-04-10 10:05 ` Pedro Alves
2015-04-10 14:03 ` Luis Machado
2015-04-13 17:51 ` Luis Machado
2015-04-14 11:31 ` Pedro Alves
2015-04-14 11:45 ` Luis Machado
2015-04-14 11:58 ` Pedro Alves
2015-04-14 12:27 ` Luis Machado
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5526B296.8040000@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox