From: "Andrew Burgess" <aburgess@broadcom.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Clear GREP_OPTIONS environment variable.
Date: Fri, 25 Mar 2011 15:46:00 -0000 [thread overview]
Message-ID: <4D8C9580.3050302@broadcom.com> (raw)
In-Reply-To: <4D81D03A.4090200@broadcom.com>
On 17/03/2011 09:11, Andrew Burgess wrote:
>
> gdb/testsuite/ChangeLog
>
> 2011-03-15 Andrew Burgess<aburgess@broadcom.com>
>
> * lib/gdb.exp (default_gdb_start,gdb_init): Clear the GREP_OPTIONS
> environment variable to make grep output more predictable. Move
> all the environment setup into gdb_init so it's done once per test
> case rather than each time we start gdb.
I committed the second version of this patch with a tiny modification, removing the "global env" line from default_gdb_start as it's no longer needed. No test regressions here.
Cheers,
Andrew
Patch as committed:
Index: ./gdb/testsuite/lib/gdb.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/lib/gdb.exp,v
retrieving revision 1.168
retrieving revision 1.169
diff -u -p -r1.168 -r1.169
--- ./gdb/testsuite/lib/gdb.exp 15 Mar 2011 16:41:42 -0000 1.168
+++ ./gdb/testsuite/lib/gdb.exp 25 Mar 2011 13:08:11 -0000 1.169
@@ -1311,25 +1311,9 @@ proc default_gdb_start { } {
global gdb_prompt
global timeout
global gdb_spawn_id;
- global env
gdb_stop_suppressing_tests;
- set env(LC_CTYPE) C
-
- # Don't let a .inputrc file or an existing setting of INPUTRC mess up
- # the test results. Even if /dev/null doesn't exist on the particular
- # platform, the readline library will use the default setting just by
- # failing to open the file. OTOH, opening /dev/null successfully will
- # also result in the default settings being used since nothing will be
- # read from this file.
- set env(INPUTRC) "/dev/null"
-
- # The gdb.base/readline.exp arrow key test relies on the standard VT100
- # bindings, so make sure that an appropriate terminal is selected.
- # The same bug doesn't show up if we use ^P / ^N instead.
- set env(TERM) "vt100"
-
verbose "Spawning $GDB $INTERNAL_GDBFLAGS $GDBFLAGS"
if [info exists gdb_spawn_id] {
@@ -2796,11 +2780,30 @@ proc gdb_init { args } {
set banned_variables_traced 1
}
- # We set LC_ALL and LANG to C so that we get the same messages as
- # expected.
+ # We set LC_ALL, LC_CTYPE, and LANG to C so that we get the same
+ # messages as expected.
setenv LC_ALL C
+ setenv LC_CTYPE C
setenv LANG C
+ # Don't let a .inputrc file or an existing setting of INPUTRC mess up
+ # the test results. Even if /dev/null doesn't exist on the particular
+ # platform, the readline library will use the default setting just by
+ # failing to open the file. OTOH, opening /dev/null successfully will
+ # also result in the default settings being used since nothing will be
+ # read from this file.
+ setenv INPUTRC "/dev/null"
+
+ # The gdb.base/readline.exp arrow key test relies on the standard VT100
+ # bindings, so make sure that an appropriate terminal is selected.
+ # The same bug doesn't show up if we use ^P / ^N instead.
+ setenv TERM "vt100"
+
+ # Some tests (for example gdb.base/maint.exp) shell out from gdb to use
+ # grep. Clear GREP_OPTIONS to make the behavoiur predictable,
+ # especially having color output turned on can cause tests to fail.
+ setenv GREP_OPTIONS ""
+
return [eval default_gdb_init $args];
}
prev parent reply other threads:[~2011-03-25 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 10:13 Andrew Burgess
2011-03-16 15:43 ` Tom Tromey
2011-03-16 16:57 ` Joel Brobecker
2011-03-17 11:25 ` Andrew Burgess
2011-03-25 15:46 ` Andrew Burgess [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=4D8C9580.3050302@broadcom.com \
--to=aburgess@broadcom.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