From: Catalin Udma <catalin.udma@freescale.com>
To: <gdb-patches@sourceware.org>
Cc: Catalin Udma <catalin.udma@freescale.com>
Subject: [PATCH] testsuite: Update py-mi-objfile to expect console format print
Date: Tue, 05 Apr 2016 10:16:00 -0000 [thread overview]
Message-ID: <1459851290-13123-1-git-send-email-catalin.udma@freescale.com> (raw)
Starting with this commit:
commit e7ea3ec7c623be0b9be1eaf4929794652a84be11
Author: Catalin Udma <catalin.udma@freescale.com>
Date: Mon Feb 29 16:16:19 2016 +0200
python: Use console format for output of gdb.execute command
the python script would use console format for gdb.execute output.
This patch fixes py-mi-objfile to expect the console format when is
checking for gdb.execute printing.
gdb/testsuite/ChangeLog:
2016-04-05 Catalin Udma <catalin.udma@freescale.com>
* gdb.python/py-mi-objfile-gdb.py: Use "list main" command
* gdb.python/py-mi-objfile-gdb.exp: Match "list main"
output in console format.
Signed-off-by: Catalin Udma <catalin.udma@freescale.com>
---
gdb/testsuite/gdb.python/py-mi-objfile-gdb.py | 2 +-
gdb/testsuite/gdb.python/py-mi-objfile.exp | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/gdb/testsuite/gdb.python/py-mi-objfile-gdb.py b/gdb/testsuite/gdb.python/py-mi-objfile-gdb.py
index 492d71c..ff1d983 100644
--- a/gdb/testsuite/gdb.python/py-mi-objfile-gdb.py
+++ b/gdb/testsuite/gdb.python/py-mi-objfile-gdb.py
@@ -24,4 +24,4 @@ import gdb
gdb.execute("set width 101", to_string=True)
# And finally a command that will use the original MI stream, which in a
# buggy gdb will use just-freed data.
-gdb.execute("list")
+gdb.execute("list main")
diff --git a/gdb/testsuite/gdb.python/py-mi-objfile.exp b/gdb/testsuite/gdb.python/py-mi-objfile.exp
index 073e4d9..bfa43a2 100644
--- a/gdb/testsuite/gdb.python/py-mi-objfile.exp
+++ b/gdb/testsuite/gdb.python/py-mi-objfile.exp
@@ -53,5 +53,6 @@ if [is_remote host] {
# PR 18833. This will cause an unpatched gdb to crash.
mi_gdb_test "-file-exec-and-symbols ${filename}" \
- ".*\\^done,line=.*${srcfile}\"" \
+ ".*main \\(.*void\\).*\
+ return 0;.*\\^done" \
"file-exec-and-symbols operation"
--
1.9.2
next reply other threads:[~2016-04-05 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 10:16 Catalin Udma [this message]
2016-04-05 10:59 ` Pedro Alves
2016-04-05 11:46 ` Catalin-Dan Udma
2016-04-05 11:59 ` Pedro Alves
2016-04-05 13:08 ` Catalin-Dan Udma
2016-04-05 13:11 ` Pedro Alves
2016-04-05 13:13 ` Pedro Alves
2016-04-05 13:36 ` Catalin-Dan Udma
2016-04-05 13:47 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1459851290-13123-1-git-send-email-catalin.udma@freescale.com \
--to=catalin.udma@freescale.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox