OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Avoid unstable test message in gdb.base/step-over-exit.exp 

Currently diffing testrun results shows:

 -PASS: gdb.base/step-over-exit.exp: break *0x7ffff77e18c6 if main == 0
 +PASS: gdb.base/step-over-exit.exp: break *0x2aaaab0988c6 if main == 0

gdb/testsuite/ChangeLog:
2017-03-08  Pedro Alves  <palves@redhat.com>

	* gdb.base/step-over-exit.exp: Add explicit test message.
This commit is contained in:
Pedro Alves 2017-03-08 22:05:36 +00:00
parent 1437d0631b
commit 1de05205af
2 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,7 @@
2017-03-08 Pedro Alves <palves@redhat.com>
* gdb.base/step-over-exit.exp: Add explicit test message.
2017-03-08 Pedro Alves <palves@redhat.com>
PR gdb/18360

3
gdb/testsuite/gdb.base/step-over-exit.exp
View File

@ -111,7 +111,8 @@ gdb_test_multiple $test $test {
}
gdb_test "break \*$syscall_insn_addr if main == 0" \
"Breakpoint \[0-9\]* at .*"
"Breakpoint \[0-9\]* at .*" \
"set conditional break at syscall address"
# Resume the child process, and the step-over is being done.