Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "J. Johnston" <jjohnstn@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: Recent MI patches broke the testsuite
Date: Mon, 16 Dec 2002 16:40:00 -0000	[thread overview]
Message-ID: <3DFE4097.10504@redhat.com> (raw)
In-Reply-To: <20021216182341.GA22508@nevyn.them.org>

Daniel Jacobowitz wrote:
> On Mon, Dec 16, 2002 at 01:24:28PM -0500, Elena Zannoni wrote:
> 
>>J. Johnston writes:
>> > My bad.  :(  The new mi-basics.exp testcase is my usual sanity test
>> > for this change.  It was updated and in fact works fine as it is expecting
>> > the new behavior.
>> > 
>> > I did not look at the correct gdb.log for the full mi testsuite.
>> > As you have noted, the lib/mi-support.exp routine mi_reinitialize_dir
>> > is using -environment-directory and is expecting the old output.
>> > 
>> > I have a patch for lib/mi=support.exp to handle the new syntax which I have
>> > included.  Since I require approval for patches I will revert the
>> > original patch and resubmit with the added change unless Elena says
>> > otherwise.
>> > 
>>
>>If this patch fixes the testsuite, no need to revert the other one,
>>just check this in. Don't forget the ChangeLog.
>>
>>Maybe Daniel can verify that it fixes his problem?
> 
> 
> Yes, it does, except for the mi-basics.exp part.  And that's minor.
> 

Great.  I have checked in the patch from the previous note.  I will
look into making the mi-basics.exp test more robust with regards
to relative paths without overly abusing .*.

-- Jeff J.




  reply	other threads:[~2002-12-16 21:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-15 13:38 Daniel Jacobowitz
2002-12-16 10:10 ` J. Johnston
2002-12-16 10:20   ` Daniel Jacobowitz
2002-12-16 10:22   ` Elena Zannoni
2002-12-16 10:34     ` Daniel Jacobowitz
2002-12-16 16:40       ` J. Johnston [this message]
2002-12-16 10:38 ` Jason Molenda

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=3DFE4097.10504@redhat.com \
    --to=jjohnstn@redhat.com \
    --cc=drow@mvista.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.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