From: Khoo Yit Phang <khooyp@cs.umd.edu>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Khoo Yit Phang <khooyp@cs.umd.edu>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add -nx for "xgdb" test in gdb/testsuite/gdb.gdb/selftest.exp
Date: Fri, 07 Sep 2012 19:27:00 -0000 [thread overview]
Message-ID: <D71D267F-E773-4811-AD56-C0B5B96F8603@cs.umd.edu> (raw)
In-Reply-To: <20120907164915.GB18234@host2.jankratochvil.net>
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
Hi Jan,
(Sorry for the resend yet again; one day, I'll get the hang this.)
On Sep 7, 2012, at 12:49 PM, Jan Kratochvil wrote:
>
> On Mon, 03 Sep 2012 04:40:27 +0200, Khoo Yit Phang wrote:
>> I found a few more tests with the same issue, here's an updated patch that
>> covers those tests.
>
> I am fine with checking in the patch if one can replace that '-nw -nx' by
> $INTERNAL_GDBFLAGS instead. If it does not work please reply here.
Ah, thanks for the info, and it works. I'll check in the updated patch later today, barring any issues.
Yit
September 7, 2012
[-- Attachment #2: xgdb-no-init.txt --]
[-- Type: text/plain, Size: 3722 bytes --]
Replace -nw option with $INTERNAL_GDBFLAGS in "xgdb" tests to avoid spurious results due to ~/.gdbinit.
gdb/testsuite/ChangeLog
2012-09-02 Khoo Yit Phang <khooyp@cs.umd.edu>
Replace -nw option with $INTERNAL_GDBFLAGS in "xgdb" tests to
avoid spurious results due to ~/.gdbinit.
* gdb.gdb/complaint.exp (setup_test): Replace -nw option with
$INTERNAL_GDBFLAGS in run command.
* gdb.gdb/observer.exp (setup_test): Ditto.
* gdb.gdb/selftest.exp (test_with_self): Ditto.
* gdb.gdb/xfullpath.exp (setup_test): Ditto.
diff --git a/gdb/testsuite/gdb.gdb/complaints.exp b/gdb/testsuite/gdb.gdb/complaints.exp
--- a/gdb/testsuite/gdb.gdb/complaints.exp
+++ b/gdb/testsuite/gdb.gdb/complaints.exp
@@ -31,6 +31,7 @@
proc setup_test { executable } {
global gdb_prompt
global timeout
+ global INTERNAL_GDBFLAGS
# load yourself into the debugger
# This can take a relatively long time, particularly for testing where
@@ -73,7 +74,7 @@
set timeout 600
set description "run until breakpoint at captured_command_loop"
- gdb_test_multiple "run -nw" "$description" {
+ gdb_test_multiple "run $INTERNAL_GDBFLAGS" "$description" {
-re "Starting program.*Breakpoint \[0-9\]+,.*captured_command_loop .data.* at .*main.c:.*$gdb_prompt $" {
pass "$description"
}
diff --git a/gdb/testsuite/gdb.gdb/observer.exp b/gdb/testsuite/gdb.gdb/observer.exp
--- a/gdb/testsuite/gdb.gdb/observer.exp
+++ b/gdb/testsuite/gdb.gdb/observer.exp
@@ -25,6 +25,7 @@
proc setup_test { executable } {
global gdb_prompt
global timeout
+ global INTERNAL_GDBFLAGS
# load yourself into the debugger
# This can take a relatively long time, particularly for testing where
@@ -67,7 +68,7 @@
set timeout 600
set description "run until breakpoint at captured_main"
- gdb_test_multiple "run -nw" "$description" {
+ gdb_test_multiple "run $INTERNAL_GDBFLAGS" "$description" {
-re "Starting program.*Breakpoint \[0-9\]+,.*captured_main .data.* at .*main.c:.*$gdb_prompt $" {
pass "$description"
}
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
@@ -242,6 +242,7 @@
global det_file
global decimal
global timeout
+ global INTERNAL_GDBFLAGS
# load yourself into the debugger
# This can take a relatively long time, particularly for testing where
@@ -303,7 +304,7 @@
set timeout 600
set description "run until breakpoint at captured_main"
- gdb_test_multiple "run -nw" "$description" {
+ gdb_test_multiple "run $INTERNAL_GDBFLAGS" "$description" {
-re "Starting program.*Breakpoint \[0-9\]+,.*captured_main .data.* at .*main.c:.*$gdb_prompt $" {
pass "$description"
}
diff --git a/gdb/testsuite/gdb.gdb/xfullpath.exp b/gdb/testsuite/gdb.gdb/xfullpath.exp
--- a/gdb/testsuite/gdb.gdb/xfullpath.exp
+++ b/gdb/testsuite/gdb.gdb/xfullpath.exp
@@ -25,6 +25,7 @@
proc setup_test { executable } {
global gdb_prompt
global timeout
+ global INTERNAL_GDBFLAGS
# load yourself into the debugger
# This can take a relatively long time, particularly for testing where
@@ -67,7 +68,7 @@
set timeout 600
set description "run until breakpoint at captured_main"
- gdb_test_multiple "run -nw" "$description" {
+ gdb_test_multiple "run $INTERNAL_GDBFLAGS" "$description" {
-re "Starting program.*Breakpoint \[0-9\]+,.*captured_main .data.* at .*main.c:.*$gdb_prompt $" {
pass "$description"
}
[-- Attachment #3: Type: text/plain, Size: 1 bytes --]
prev parent reply other threads:[~2012-09-07 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 15:00 Khoo Yit Phang
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 [this message]
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=D71D267F-E773-4811-AD56-C0B5B96F8603@cs.umd.edu \
--to=khooyp@cs.umd.edu \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/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