From: Yao Qi <yao@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: [Patch, Testsuite] Update selftest.exp to match c source
Date: Tue, 17 Aug 2010 06:19:00 -0000 [thread overview]
Message-ID: <20100817061849.GA30599@qiyaows> (raw)
[-- Attachment #1: Type: text/plain, Size: 234 bytes --]
This patch is to update gdb.gdb/selftest.exp to reflect the latest
source file, otherwise, it will fail in some cases due to failing to
match source code.
Is that OK?
--
Yao Qi
CodeSourcery
yao@codesourcery.com
(650) 331-3385 x739
[-- Attachment #2: selftest.patch --]
[-- Type: text/x-diff, Size: 1213 bytes --]
gdb/testsuite/
2010-08-17 Yao Qi <yao@codesourcery.com>
* gdb.gdb/selftest.exp (do_steps_and_nexts): Update test case
to reflect latest c source file.
Index: gdb/testsuite/gdb.gdb/selftest.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.gdb/selftest.exp,v
retrieving revision 1.24
diff -u -p -r1.24 selftest.exp
--- gdb/testsuite/gdb.gdb/selftest.exp 26 Jun 2010 06:44:47 -0000 1.24
+++ gdb/testsuite/gdb.gdb/selftest.exp 17 Aug 2010 05:58:37 -0000
@@ -185,11 +185,15 @@ proc do_steps_and_nexts {} {
set description "step over instream initialization"
set command "step"
}
- -re ".*getcwd .gdb_dirbuf, sizeof .gdb_dirbuf..;.*$gdb_prompt $" {
+ -re ".*getcwd .gdb_dirbuf, sizeof .gdb_dirbuf.*$gdb_prompt $" {
set description "next over getcwd"
set command "next"
}
- -re ".*quit_flag = 0.*$gdb_prompt $" {
+ -re ".*gdb_program_name = xstrdup.*$gdb_prompt $" {
+ set description "next over xstrdup"
+ set command "next"
+ }
+ -re ".*quit_flag = 0.*$gdb_prompt $" {
set description "step over quit_flag initialization"
set command "step"
}
next reply other threads:[~2010-08-17 6:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 6:19 Yao Qi [this message]
2010-08-17 8:10 ` Joel Brobecker
2010-08-18 2:31 ` Yao Qi
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=20100817061849.GA30599@qiyaows \
--to=yao@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).