* [PATCH] test, btrace: update expected text
@ 2014-01-16 8:58 Markus Metzger
2014-01-16 9:23 ` Pedro Alves
0 siblings, 1 reply; 2+ messages in thread
From: Markus Metzger @ 2014-01-16 8:58 UTC (permalink / raw)
To: jan.kratochvil, palves; +Cc: gdb-patches
The error message for starting recording twice changed.
Update the expected text to fix resulting regressions.
2014-01-16 Markus Metzger <markus.t.metzger@intel.com>
* gdb.btrace/enable.exp: Update expected text.
---
gdb/testsuite/gdb.btrace/enable.exp | 6 +++---
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/gdb/testsuite/gdb.btrace/enable.exp b/gdb/testsuite/gdb.btrace/enable.exp
index 5fff2ff..78c7e53 100644
--- a/gdb/testsuite/gdb.btrace/enable.exp
+++ b/gdb/testsuite/gdb.btrace/enable.exp
@@ -50,10 +50,10 @@ gdb_test "record function-call-history" "No trace\\." "record function-call-hist
gdb_test "record instruction-history" "No trace\\." "record instruction-history without trace"
# btrace cannot be enabled twice
-gdb_test "record btrace" "The process is already being recorded\\." "record btrace the second time"
+gdb_test "record btrace" "The process is already being recorded\\. Use \"record stop\" to stop recording first\\." "record btrace the second time"
# full record cannot be activated as long as btrace is active
-gdb_test "record full" "Process record target already running\\. Use \"record stop\" to stop record target first\\." "record full cannot be enabled"
+gdb_test "record full" "The process is already being recorded\\. Use \"record stop\" to stop recording first\\." "record full cannot be enabled"
# no trace recorded yet
gdb_test "info record" "Active record target: record-btrace\r\nRecorded 0 instructions in 0 functions for thread 1.*\\." "info record without trace"
@@ -64,7 +64,7 @@ gdb_test "record stop" "No record target is currently active\\..*" "record stop
# enable btrace again
gdb_test_no_output "record btrace" "record btrace re-enable"
-gdb_test "record btrace" "The process is already being recorded\\." "record btrace re-enable twice"
+gdb_test "record btrace" "The process is already being recorded\\. Use \"record stop\" to stop recording first\\." "record btrace re-enable twice"
# continue to the end and make sure we don't die
gdb_test "continue" ".*Inferior.*exited.*" "continue to end"
--
1.8.3.1
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] test, btrace: update expected text
2014-01-16 8:58 [PATCH] test, btrace: update expected text Markus Metzger
@ 2014-01-16 9:23 ` Pedro Alves
0 siblings, 0 replies; 2+ messages in thread
From: Pedro Alves @ 2014-01-16 9:23 UTC (permalink / raw)
To: Markus Metzger; +Cc: jan.kratochvil, gdb-patches
On 01/16/2014 08:58 AM, Markus Metzger wrote:
> The error message for starting recording twice changed.
> Update the expected text to fix resulting regressions.
>
> 2014-01-16 Markus Metzger <markus.t.metzger@intel.com>
>
> * gdb.btrace/enable.exp: Update expected text.
OK, thanks.
Sorry I missed this, the btrace tests are skipped on my
box (because it doesn't support btrace)...
--
Pedro Alves
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-01-16 9:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-01-16 8:58 [PATCH] test, btrace: update expected text Markus Metzger
2014-01-16 9:23 ` Pedro Alves
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).