Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Sandra Loosemore <sandra@codesourcery.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] testsuite: Disable parts of gdb.base/source-dir.exp on remote host.
Date: Sat, 20 Jun 2020 18:54:26 +0100	[thread overview]
Message-ID: <c6549a50-796b-d346-875f-16aeb63ba5af@redhat.com> (raw)
In-Reply-To: <6ac784c5-25e4-c2b5-06e1-9fd527533e4d@codesourcery.com>

On 6/20/20 6:44 PM, Sandra Loosemore wrote:
> One set of tests in gdb.base/source-dir.exp does a lot of complicated directory manipulations to force a specific DW_AT_comp_dir format and gdb directory search path.  As it's written, everything assumes host == build, and it does not seem to me that there is any obvious way to rewrite this so it will work in general on remote host.  For instance, our harness for testing on remote Windows host normally does all compilation and GDB execution in $cwd using relative pathnames and I'm not sure all these directory tricks would set up the scenario it's trying to test even if they were correctly performed on host rather than build.  So I think it's reasonable just to disable this on remote host instead.
> 
> I also noted that it's using the wrong search path syntax for Windows host in the "set directories" command and conditionalized that while I was looking at it.  That's a necessary fix to make this work in a situation where host == build and it's Windows, but I'm not actually set up to test that it's sufficient, too.
> 
> OK to check this in?

This is OK, but please make sure that the info above ends up
in the commit log as well (wrapped at 72-character columns per
standard git convention).  

(Nit -- convention is to not end the subject line with a period.)

Thanks,
Pedro Alves



      reply	other threads:[~2020-06-20 17:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-20 17:44 Sandra Loosemore
2020-06-20 17:54 ` Pedro Alves [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=c6549a50-796b-d346-875f-16aeb63ba5af@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sandra@codesourcery.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