From: Denis PILAT <denis.pilat@st.com>
To: gdb-patches <gdb-patches@sourceware.org>
Subject: [RFA] re-initialize height to 0 during setshow.exp
Date: Mon, 02 Apr 2007 14:57:00 -0000 [thread overview]
Message-ID: <461119CA.6060509@st.com> (raw)
In testsuite/gdb.base/setshow.exp, after "set height 100", it could
occur that following commands require user interaction to proceed like:
---Type <return> to continue, or q <return> to quit---
(At least it's the case for our gdb in "show user" since we have defined
a lot of user command.)
Attach is a patch that fixes a problem in this test.
We could also add
gdb_test "set height 0" "" "set height 0"
or increase the height to a very large number, but I prefer to reset
height to 0 like done in gdb.exp.
--
Denis
2007-04-02 Denis Pilat <denis.pilat@st.com>
* gdb.base/setshow.exp: Reset height to 0 after having set it to 100.
Index: testsuite/gdb.base/setshow.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/setshow.exp,v
retrieving revision 1.5
diff -u -p -r1.5 setshow.exp
--- testsuite/gdb.base/setshow.exp 9 Jan 2007 17:59:11 -0000 1.5
+++ testsuite/gdb.base/setshow.exp 2 Apr 2007 14:46:58 -0000
@@ -155,6 +155,16 @@ gdb_test "show environment FOOBARBAZ" "F
gdb_test "set height 100" "" "set height 100"
#test show height 100
gdb_test "show height" "Number of lines gdb thinks are in a page is 100..*" "show height"
+
+# back to infinite height to avoid pagers
+send_gdb "set height 0\n"
+ gdb_expect 10 {
+ -re "$gdb_prompt $" {}
+ timeout {
+ warning "Couldn't set the height to 0"
+ }
+}
+
#test set history expansion on
gdb_test "set history expansion on" "" "set history expansion on"
#test show history expansion on
next reply other threads:[~2007-04-02 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 14:57 Denis PILAT [this message]
2007-04-02 17:56 ` Michael Snyder
2007-04-03 13:26 ` Denis PILAT
2007-04-03 14:34 ` Daniel Jacobowitz
2007-04-03 14:53 ` Denis PILAT
2007-04-10 15:14 ` Daniel Jacobowitz
2007-04-16 13:50 ` Denis PILAT
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=461119CA.6060509@st.com \
--to=denis.pilat@st.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