From: Jie Zhang <jie.zhang@analog.com>
To: gdb-patches@sourceware.org
Subject: Testsuite: Don't use global command in gdb_expect
Date: Mon, 15 Dec 2008 06:07:00 -0000 [thread overview]
Message-ID: <4945F3EF.6050004@analog.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
The Tcl global command has no effect unless executed in the context of a
proc body. So the global commands in the following code are useless.
Even worse, they would cause unexpected result. When gdb_expect gets
something containing "global", it will try to execute hex as a command,
which will cause an error.
gdb_expect {
global hex
global nl
global bp_addr
global gdb_prompt
-re "$hex.*${nl}($hex).*$gdb_prompt $" {
set bp_addr $expect_out(1,string)
pass "get breakpoint address for foo"
}
-re ".*$gdb_prompt $" {
fail "get breakpoint address for foo"
return 0;
}
timeout {
fail "get breakpoint address for foo (timeout)"
return 0;
}
}
This patch should fix this issue. Is it OK?
Thanks,
Jie
[-- Attachment #2: gdb-testsuite-consecutive.diff --]
[-- Type: text/x-patch, Size: 719 bytes --]
2008-12-15 Jie Zhang <jie.zhang@analog.com>
* gdb.base/consecutive.exp: Don't use global in gdb_expect.
Index: gdb.base/consecutive.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/consecutive.exp,v
retrieving revision 1.7
diff -u -p -r1.7 consecutive.exp
--- gdb.base/consecutive.exp 6 Aug 2008 12:52:07 -0000 1.7
+++ gdb.base/consecutive.exp 15 Dec 2008 05:51:49 -0000
@@ -64,11 +64,6 @@ set stop_addr 0
send_gdb "x /2i \$pc\n"
gdb_expect {
- global hex
- global nl
- global bp_addr
- global gdb_prompt
-
-re "$hex.*${nl}($hex).*$gdb_prompt $" {
set bp_addr $expect_out(1,string)
pass "get breakpoint address for foo"
next reply other threads:[~2008-12-15 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 6:07 Jie Zhang [this message]
2008-12-15 7:53 ` Joel Brobecker
2008-12-15 8:50 ` Andreas Schwab
2008-12-15 13:16 ` Jie Zhang
2008-12-18 19:57 ` Michael Snyder
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=4945F3EF.6050004@analog.com \
--to=jie.zhang@analog.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