From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 2/4] list.exp: Adjust "set listsize -1" to current test source's real line count.
Date: Thu, 28 Mar 2013 06:09:00 -0000 [thread overview]
Message-ID: <20130327204411.24420.47306.stgit@brno.lan> (raw)
In-Reply-To: <20130327204357.24420.94722.stgit@brno.lan>
The "set listsize -1" test in list.exp can't work correct anymore
nowadays, because the test's source files grew over time, and this
particular test was never updated.
This fixes it in the obvious way.
gdb/testsuite/
2013-03-21 Pedro Alves <palves@redhat.com>
* gdb.base/list.exp (test_listsize): Adjust test to make sure we
list the whole file.
---
gdb/testsuite/gdb.base/list.exp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/testsuite/gdb.base/list.exp b/gdb/testsuite/gdb.base/list.exp
index 8684b0c..97cca91 100644
--- a/gdb/testsuite/gdb.base/list.exp
+++ b/gdb/testsuite/gdb.base/list.exp
@@ -138,7 +138,7 @@ proc test_listsize {} {
set_listsize -1
setup_xfail "*-*-*"
- gdb_test "list 1" "1\[ \t\]+#include .*\r\n39\[ \t\]+\}" "list line 1 with unlimited listsize"
+ gdb_test "list 1" "1\[ \t\]+#include .*\r\n43\[ \t\]+\}" "list line 1 with unlimited listsize"
}
#
next prev parent reply other threads:[~2013-03-27 20:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 6:28 [PATCH 0/4 v2] [mainline+7.6] PR gdb/15294: list with unlimited listsize broken Pedro Alves
2013-03-28 1:11 ` [PATCH 1/4] list.exp: Catch "set listsize" failures (and "set listsize -1/0"'s history) Pedro Alves
2013-03-28 6:09 ` Pedro Alves [this message]
2013-03-28 7:44 ` [PATCH 3/4] list.exp: Avoid hardcoding line numbers Pedro Alves
2013-03-28 9:12 ` [PATCH 4/4] Fix PR gdb/15294: list with unlimited listsize broken Pedro Alves
2013-03-28 9:26 ` Pedro Alves
2013-03-28 16:47 ` Pedro Alves
2013-03-28 15:39 ` [PATCH 0/4 v2] [mainline+7.6] " 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=20130327204411.24420.47306.stgit@brno.lan \
--to=palves@redhat.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