Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Set EDITOR to true before using edit
Date: Wed, 11 Mar 2020 01:10:05 -0400	[thread overview]
Message-ID: <f452e082-a14c-8afe-6c69-817435fcaae2@simark.ca> (raw)
In-Reply-To: <20200310163222.GA2202@delia>

On 2020-03-10 12:32 p.m., Tom de Vries wrote:
> Hi,
> 
> The test-case gdb.base/list-ambiguous.exp normally passes, but with target
> board readnow, some tests fail.
> 
> In particular, for this test, edit doesn't fail as expected:
> ...
>     # While at it, test the "edit" command as well, since it shares
>     # code with "list".
>     gdb_test "edit $symbol" \
>         "Specified line is ambiguous:\r\n${h0_re}\r\n${h1_re}"
> ...
> and the editor is launched, in my case:
> ...
> $ echo $EDITOR
> /home/vries/bin/emacs-nw.sh
> ...
> which result in all subsequent tests failing with timeout, and an editor
> backup file in my sources:
> ...
> $ git status --ignored
> On branch master
> Ignored files:
>   (use "git add -f <file>..." to include in what will be committed)
> 
>         gdb/testsuite/gdb.base/#list-ambiguous0.c#
> 
> nothing to commit, working tree clean
> ...
> 
> Fix this by setting EDITOR to true before starting gdb in this test-case.
> 
> Tested on x86_64-linux.
> 
> OK for trunk?
> 
> Thanks,
> - Tom
> 
> [gdb/testsuite] Set EDITOR to true before using edit
> 
> gdb/testsuite/ChangeLog:
> 
> 2020-03-10  Tom de Vries  <tdevries@suse.de>
> 
> 	* gdb.base/list-ambiguous.exp: Set EDITOR to true.
> 
> ---
>  gdb/testsuite/gdb.base/list-ambiguous.exp | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/gdb/testsuite/gdb.base/list-ambiguous.exp b/gdb/testsuite/gdb.base/list-ambiguous.exp
> index 8d63938fb7..0c89bba3a1 100644
> --- a/gdb/testsuite/gdb.base/list-ambiguous.exp
> +++ b/gdb/testsuite/gdb.base/list-ambiguous.exp
> @@ -18,6 +18,8 @@
>  
>  standard_testfile list-ambiguous0.c list-ambiguous1.c
>  
> +setenv EDITOR true
> +
>  if {[prepare_for_testing "failed to prepare" $testfile [list $srcfile $srcfile2] \
>  	 {debug}]} {
>      return -1
> 

That's a fun one :).

This is fine, but please add a comment on top of your setenv to explain why
it's there.

Simon


      parent reply	other threads:[~2020-03-11  5:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 16:32 Tom de Vries
2020-03-11  0:05 ` Tom Tromey
2020-03-11  5:10 ` Simon Marchi [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=f452e082-a14c-8afe-6c69-817435fcaae2@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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