Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <lgustavo@codesourcery.com>
To: Pedro Alves <palves@redhat.com>
Cc: "'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [PATCH, testsuite] Fix subst.exp failure when GDB is configured with --with-relocated-sources
Date: Wed, 19 Jun 2013 21:04:00 -0000	[thread overview]
Message-ID: <51C2168E.2070406@codesourcery.com> (raw)
In-Reply-To: <51C21101.1090904@redhat.com>

On 06/19/2013 05:13 PM, Pedro Alves wrote:
> On 06/19/2013 08:43 PM, Luis Machado wrote:
>> Hi,
>>
>> The gdb.base/subst.exp test assumes GDB starts with no default
>> substitution rules, which is not true if GDB has been configured with
>> --with-relocated-sources. In that case we start with a default rule,
>> causing the first test (checking that there are no rules) to fail.
>>
>> This patch clears any default substitution rules that may exist prior to
>> doing all the other tests.
>>
>> OK?
>>
>
> Looks obviously correct to me.
>

Thanks. Checked in.


      reply	other threads:[~2013-06-19 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19 20:14 Luis Machado
2013-06-19 20:37 ` Pedro Alves
2013-06-19 21:04   ` Luis Machado [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=51C2168E.2070406@codesourcery.com \
    --to=lgustavo@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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