Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Bob Rossi <bob_rossi@cox.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix spurious mi-basics.exp failures
Date: Sat, 06 May 2006 19:52:00 -0000	[thread overview]
Message-ID: <20060506195235.GA28874@nevyn.them.org> (raw)
In-Reply-To: <200605061657.k46GvXbh020454@d12av02.megacenter.de.ibm.com>

On Sat, May 06, 2006 at 06:57:33PM +0200, Ulrich Weigand wrote:
> Daniel Jacobowitz wrote:
> 
> > On Fri, May 05, 2006 at 10:02:37PM -0400, Bob Rossi wrote:
> > > I can't think of exactly how the anchoring would have just anything
> > > related to these tests.  I'm just wondering, what fixed the 
> > > relative/absolute path problem?
> > 
> > My point is that before the anchoring, the "^done" pattern probably
> > matched "203^done" in the output.
> > 
> > They're still broken if you configure with a relative path, which you
> > can see from your output:
> 
> That sounds like a reasonable explanation.  I've always had to configure
> with an absolute path, or else these tests would fail.  However, since
> some time the tests fail even when configuring with an absolute path.
> The patch I'm proposing gets them back to passing in that case (with
> relative path they still fail).
> 
> Is the patch OK then?

Yes, it is.  Thanks a lot.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2006-05-06 19:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-06  1:19 Ulrich Weigand
2006-05-06  1:28 ` Bob Rossi
2006-05-06  1:52 ` Daniel Jacobowitz
2006-05-06  2:02   ` Bob Rossi
2006-05-06  4:08     ` Daniel Jacobowitz
2006-05-06 16:57       ` Ulrich Weigand
2006-05-06 19:52         ` Daniel Jacobowitz [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=20060506195235.GA28874@nevyn.them.org \
    --to=drow@false.org \
    --cc=bob_rossi@cox.net \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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