public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/18003] New: Some fails in gdb.base/breakpoint-in-ro-region.exp
@ 2015-02-20 12:41 qiyao at gcc dot gnu.org
2015-02-20 18:20 ` [Bug gdb/18003] " qiyao at gcc dot gnu.org
0 siblings, 1 reply; 2+ messages in thread
From: qiyao at gcc dot gnu.org @ 2015-02-20 12:41 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=18003
Bug ID: 18003
Summary: Some fails in gdb.base/breakpoint-in-ro-region.exp
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: qiyao at gcc dot gnu.org
I see some fails as below on aarch64-linux-gnu target, in both remote and
native testing...
si^M
0x0000000000400738 23 i = 0;^M
(gdb) FAIL: gdb.base/breakpoint-in-ro-region.exp: always-inserted off: auto-hw
off: step in ro region
si^M
0x0000000000400740 24 i = 0;^M
(gdb) FAIL: gdb.base/breakpoint-in-ro-region.exp: always-inserted on: auto-hw
off: step in ro region
looks the hex is unexpected to the pattern matching,
set test "step in ro region"
gdb_test_multiple "si" $test {
-re "Could not insert hardware breakpoints.*$gdb_prompt $" {
gdb_assert {!$hw_step && $auto_hw == "on" && !$supports_hbreak} \
"$test (cannot insert hw break)"
}
-re "Cannot set software breakpoint at read-only address
$next_insn.*$gdb_prompt $" {
gdb_assert {!$hw_step && $auto_hw == "off"} \
"$test (cannot insert sw break)"
}
-re "^si\r\nNote: automatically using hardware breakpoints for read-only
addresses\.\r\n${decimal}\[ \t\]+i = 0;\r\n$gdb_prompt $" {
gdb_assert {!$hw_step && $auto_hw == "on" && $supports_hbreak} \
"$test (auto-hw)"
}
-re "^si\r\n${decimal}\[ \t\]+i = 0;\r\n$gdb_prompt $" {
gdb_assert {$hw_step || ($auto_hw == "on" && $supports_hbreak)} \
"$test (no error)"
}
}
further analysis is needed.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug gdb/18003] Some fails in gdb.base/breakpoint-in-ro-region.exp
2015-02-20 12:41 [Bug gdb/18003] New: Some fails in gdb.base/breakpoint-in-ro-region.exp qiyao at gcc dot gnu.org
@ 2015-02-20 18:20 ` qiyao at gcc dot gnu.org
0 siblings, 0 replies; 2+ messages in thread
From: qiyao at gcc dot gnu.org @ 2015-02-20 18:20 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=18003
Yao Qi <qiyao at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |aarch64-linux-gnu
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-02-20 12:41 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-20 12:41 [Bug gdb/18003] New: Some fails in gdb.base/breakpoint-in-ro-region.exp qiyao at gcc dot gnu.org
2015-02-20 18:20 ` [Bug gdb/18003] " qiyao at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).