From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-54545-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 24935 invoked by alias); 14 Mar 2008 18:07:56 -0000
Received: (qmail 24927 invoked by uid 22791); 14 Mar 2008 18:07:56 -0000
X-Spam-Check-By: sourceware.org
Received: from qnxmail.qnx.com (HELO qnxmail.qnx.com) (209.226.137.76)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 14 Mar 2008 18:07:34 +0000
Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.42.96.5]) 	by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id NAA21847; 	Fri, 14 Mar 2008 13:48:33 -0400
Received: from [10.42.100.129] (dhcp-100-129 [10.42.100.129]) by smtp.ott.qnx.com (8.8.8/8.6.12) with ESMTP id NAA27336; Fri, 14 Mar 2008 13:07:31 -0500
Message-ID: <47DABEE2.70405@qnx.com>
Date: Fri, 14 Mar 2008 18:07:00 -0000
From: Aleksandar Ristovski <aristovski@qnx.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Daniel Jacobowitz <drow@false.org>
CC: Vladimir Prus <ghost@cs.msu.su>, gdb-patches@sources.redhat.com
Subject: Re: [RFC] gdb.mi tests
References: <47D6DE48.8090003@qnx.com> <47D82C77.8020705@qnx.com> <fr9amm$fiu$1@ger.gmane.org> <20080312193423.GA837@caradoc.them.org> <47D841C4.4040004@qnx.com> <20080312210431.GA5503@caradoc.them.org>
In-Reply-To: <20080312210431.GA5503@caradoc.them.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2008-03/txt/msg00187.txt.bz2

Daniel Jacobowitz wrote:
> On Wed, Mar 12, 2008 at 04:49:08PM -0400, Aleksandar Ristovski wrote:
>> This means that the order in which files are loaded matters and the latter 
>> in the process a file gets loaded, it carries more 'overriding' 
>> capabilities. Therefore, first files loaded should be very generic, going 
>> towards customization files.
> 
> Yes.  But load_lib will not reload an already loaded file - we have
> some board files which check if $tool == "gdb", and load_lib
> mi-support.exp themselves, and use "rename".  I didn't say it was
> pretty or the right way!
> 

True. It means that load_lib mi-support.exp can safely stay in the testcases, 
and who needs to override something from there should add 'load_lib 
mi-support.exp' in their baseboard file and then rewrite the function (or use 
rename) after load_lib.

I would still like to see changes to mi-support.exp go in to make it more 
in-line with gdb.exp; I think "rename" would be avoided in most of the cases.

Nothing critical though...