Handle memory write errors on gdb.base/break-always.exp
authorLuis Machado <lgustavo@codesourcery.com>
Wed, 29 Apr 2015 15:09:40 +0000 (12:09 -0300)
committerLuis Machado <lgustavo@codesourcery.com>
Wed, 29 Apr 2015 15:09:40 +0000 (12:09 -0300)
commitecbf2b3c4f5ee6c00cf058b87fa49708d4030d7f
tree088ad98a585552c4f7ef172cad7a919fe4df064c
parent0a13382c8e708fd9eb15dbc81cedc35e6670090c
Handle memory write errors on gdb.base/break-always.exp

This is another case of the testcase not handling memory write errors that
happen on some targets (QEMU) when GDB attempts to modify an address that
should contain a breakpoint, for example.

The following patch handles this and prevents spurious failures from
happening. It also adds a foreach loop to avoid duplication of code
and hardcoded patterns.

gdb/testsuite/ChangeLog:

2015-04-29  Luis Machado  <lgustavo@codesourcery.com>

* gdb.base/break-always.exp: Abort testing if writing to memory
causes an error.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.base/break-always.exp
This page took 0.025654 seconds and 4 git commands to generate.