testsuite/gdb.trace: Fix expected message on continue.
authorMarcin Kościelnicki <koriakin@0x04.net>
Tue, 19 Jan 2016 11:30:34 +0000 (12:30 +0100)
committerMarcin Kościelnicki <koriakin@0x04.net>
Tue, 19 Jan 2016 12:04:58 +0000 (13:04 +0100)
commitbd0a71fa16f668341a9361c695bc3ca44d27b322
tree41fb8ec38c605a128732e9f3967a573fc26cb32b
parenta4af960aef09b7c0258b60954332969ef6d0cd3a
testsuite/gdb.trace: Fix expected message on continue.

This is fallout from f303dbd60d9c7984832446eeb9d4e4d89703c615.

The testcases themselves are single-threaded, but they load the IPA library,
which injects a thread in the inferior - making them multithreaded.
This results in printing the thread numbers in breakpoint messages.

gdb/testsuite/ChangeLog:

* gdb.trace/ftrace.exp: Fix expected message on continue.
* gdb.trace/pending.exp: Fix expected message on continue.
* gdb.trace/trace-break.exp: Fix expected message on continue.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.trace/ftrace.exp
gdb/testsuite/gdb.trace/pending.exp
gdb/testsuite/gdb.trace/trace-break.exp