I noticed there was an unexpected pass in mi-watch.exp when running on
x86_64. Doing a bit of archeology shows that the xfail was added by
4a543da. This particular test failed on the MIPS architecture, which
the original contributor was working with. Here is the thread:
https://www.sourceware.org/ml/gdb-patches/2007-09/msg00151.html
Looking at the latest buildbot results for MIPS, it seems that it's also
an unexpected pass on that architecture. Therefore, I see no reason to
leave the xfail in place.
gdb/testsuite/ChangeLog:
* gdb.mi/mi-watch.exp (test_watchpoint_triggering): Remove xfail.
+2015-07-27 Simon Marchi <simon.marchi@ericsson.com>
+
+ * gdb.mi/mi-watch.exp (test_watchpoint_triggering): Remove xfail.
+
2015-07-27 Patrick Palka <patrick@parcs.ath.cx>
* gdb.base/gdb-sigterm-2.exp: New test.
{"" "wpt=\{number=\"2\",exp=\"C\"\},value=\{old=\".*\",new=\"3\"\}"} \
"watchpoint trigger"
- if { $type == "sw" } {
- setup_xfail *-*-*
- }
mi_execute_to "exec-continue" "watchpoint-scope" "callee3" ".*" \
".*basics.c" $line_callee3_close_brace \
{"" "wpnum=\"2\""} \
"watchpoint trigger"
- clear_xfail *-*-*
}
proc test_watchpoint_all {type} {