public inbox for archer-commits@sourceware.org help / color / mirror / Atom feed
From: jkratoch@sourceware.org To: archer-commits@sourceware.org Subject: [SCM] archer-jankratochvil-watchpoint3: Merge branch 'f-cleanup-fork-multifix' into archer-jankratochvil-watchpoint3 Date: Fri, 20 Jan 2012 01:30:00 -0000 [thread overview] Message-ID: <20120120013055.24574.qmail@sourceware.org> (raw) The branch, archer-jankratochvil-watchpoint3 has been updated via 9ffdb81bc216f908184b56c00ad44ef0246c2121 (commit) via 04317efd12001065c1288f495fd25e0bedc81170 (commit) from f1bda6d1a418bddf2bdd569dd735bcf5ed525c32 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email. - Log ----------------------------------------------------------------- commit 9ffdb81bc216f908184b56c00ad44ef0246c2121 Merge: f1bda6d 04317ef Author: Jan Kratochvil <jan.kratochvil@redhat.com> Date: Fri Jan 20 02:30:49 2012 +0100 Merge branch 'f-cleanup-fork-multifix' into archer-jankratochvil-watchpoint3 commit 04317efd12001065c1288f495fd25e0bedc81170 Author: Jan Kratochvil <jan.kratochvil@redhat.com> Date: Fri Jan 20 02:30:44 2012 +0100 . ----------------------------------------------------------------------- Summary of changes: gdb/testsuite/gdb.multi/watchpoint-multi.exp | 21 +++++++++++++-------- 1 files changed, 13 insertions(+), 8 deletions(-) First 500 lines of diff: diff --git a/gdb/testsuite/gdb.multi/watchpoint-multi.exp b/gdb/testsuite/gdb.multi/watchpoint-multi.exp index 93245f1..92a81f7 100644 --- a/gdb/testsuite/gdb.multi/watchpoint-multi.exp +++ b/gdb/testsuite/gdb.multi/watchpoint-multi.exp @@ -69,18 +69,23 @@ gdb_breakpoint "marker_exit" gdb_test "inferior 1" "witching to inferior 1 .*" -gdb_test "awatch b" "Hardware access \\(read/write\\) watchpoint \[0-9\]+: b" +if [skip_hw_watchpoint_multi_tests] { + # On single hardware watchpoint at least test the watchpoint in inferior + # 2 is not hit. +} else { + gdb_test "awatch b" "Hardware access \\(read/write\\) watchpoint \[0-9\]+: b" -gdb_test "inferior 2" "witching to inferior 2 .*" + gdb_test "inferior 2" "witching to inferior 2 .*" -# FAIL would be a hit on watchpoint for `b' - that one is for the other -# inferior. -gdb_test "continue" "Hardware access \\(read/write\\) watchpoint \[0-9\]+: c\r\n\r\nOld value = 0\r\nNew value = 3\r\n.*" "catch c" + # FAIL would be a hit on watchpoint for `b' - that one is for the other + # inferior. + gdb_test "continue" "Hardware access \\(read/write\\) watchpoint \[0-9\]+: c\r\n\r\nOld value = 0\r\nNew value = 3\r\n.*" "catch c" -gdb_test "continue" "Breakpoint \[0-9\]+, marker_exit .*" "catch marker_exit in inferior 2" + gdb_test "continue" "Breakpoint \[0-9\]+, marker_exit .*" "catch marker_exit in inferior 2" -gdb_test "inferior 1" "witching to inferior 1 .*" + gdb_test "inferior 1" "witching to inferior 1 .*" -gdb_test "continue" "Hardware access \\(read/write\\) watchpoint \[0-9\]+: b\r\n\r\nOld value = 0\r\nNew value = 2\r\n.*" "catch b" + gdb_test "continue" "Hardware access \\(read/write\\) watchpoint \[0-9\]+: b\r\n\r\nOld value = 0\r\nNew value = 2\r\n.*" "catch b" +} gdb_test "continue" "Breakpoint \[0-9\]+, marker_exit .*" "catch marker_exit in inferior 1" hooks/post-receive -- Repository for Project Archer.
next reply other threads:[~2012-01-20 1:30 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-20 1:30 jkratoch [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-01-30 16:58 jkratoch 2012-01-24 14:19 jkratoch 2012-01-20 20:16 jkratoch 2012-01-20 11:07 jkratoch 2012-01-20 1:20 jkratoch 2012-01-05 9:18 jkratoch 2012-01-02 22:43 jkratoch 2012-01-02 16:46 jkratoch 2012-01-02 15:19 jkratoch 2011-12-26 23:24 jkratoch 2011-12-26 22:04 jkratoch 2011-12-26 20:32 jkratoch 2011-12-26 19:28 jkratoch
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=20120120013055.24574.qmail@sourceware.org \ --to=jkratoch@sourceware.org \ --cc=archer-commits@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).