gdb/testsuite: do not hard-code location indices in condbreak-multi-context.exp
authorTankut Baris Aktemur <tankut.baris.aktemur@intel.com>
Tue, 24 Nov 2020 08:56:38 +0000 (09:56 +0100)
committerTankut Baris Aktemur <tankut.baris.aktemur@intel.com>
Tue, 24 Nov 2020 08:57:31 +0000 (09:57 +0100)
commit50757f95a8296b3552362d9d6ac6c0182336766f
tree9c4090ddc838868cd326480f0f92864934909b10
parent2c20a6018c56797f4ce9c2d3c462168cb2d76831
gdb/testsuite: do not hard-code location indices in condbreak-multi-context.exp

Breakpoint locations are sorted according to their addresses.  The
addresses are determined by how the compiler emits the code.
Therefore, we may have a different order of locations depending on the
compiler we use.  To make the gdb.base/condbreak-multi-context.exp
test flexible enough for different compilers' output, do not hard-code
location indices.

Tested with GCC and Clang.

gdb/testsuite/ChangeLog:
2020-11-24  Tankut Baris Aktemur  <tankut.baris.aktemur@intel.com>

* gdb.base/condbreak-multi-context.exp: Do not hard-code location
indices.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.base/condbreak-multi-context.exp