From: Khoo Yit Phang <khooyp@cs.umd.edu>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: Khoo Yit Phang <khooyp@cs.umd.edu>
Subject: [PATCH] Add -nx for "xgdb" test in gdb/testsuite/gdb.gdb/selftest.exp
Date: Sat, 01 Sep 2012 15:00:00 -0000 [thread overview]
Message-ID: <387EE3E3-80B3-42E0-AFE7-1BAA78B422D3@cs.umd.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 230 bytes --]
Hi,
The "xgdb" test in gdb/testsuite/gdb.gdb/selftest.exp was giving me spurious results since it was loading ~/.gdbinit. Here's a patch that adds the -nx option to prevent this problem.
Thanks,
Yit
September 1, 2012
[-- Attachment #2: xgdb-no-init.txt --]
[-- Type: text/plain, Size: 763 bytes --]
gdb/ChangeLog:
2012-09-01 Khoo Yit Phang <khooyp@cs.umd.edu>
Add -nx option to "xgdb" test to prevent spurious results
due to ~/.gdbinit.
* testsuite/gdb.gdb/selftest.exp: (run until breakpoint at
captured_main) Add -nx option.
diff --git a/gdb/testsuite/gdb.gdb/selftest.exp b/gdb/testsuite/gdb.gdb/selftest.exp
--- a/gdb/testsuite/gdb.gdb/selftest.exp
+++ b/gdb/testsuite/gdb.gdb/selftest.exp
@@ -303,7 +303,7 @@
set timeout 600
set description "run until breakpoint at captured_main"
- gdb_test_multiple "run -nw" "$description" {
+ gdb_test_multiple "run -nw -nx" "$description" {
-re "Starting program.*Breakpoint \[0-9\]+,.*captured_main .data.* at .*main.c:.*$gdb_prompt $" {
pass "$description"
}
next reply other threads:[~2012-09-01 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 15:00 Khoo Yit Phang [this message]
2012-09-03 2:40 ` Khoo Yit Phang
2012-09-06 17:09 ` Khoo Yit Phang
2012-09-07 16:49 ` Jan Kratochvil
2012-09-07 19:27 ` Khoo Yit Phang
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=387EE3E3-80B3-42E0-AFE7-1BAA78B422D3@cs.umd.edu \
--to=khooyp@cs.umd.edu \
--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