From: Aleksandar Ristovski <aristovski@qnx.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb-patches@sources.redhat.com
Subject: Re: [RFC] gdb.mi tests
Date: Fri, 14 Mar 2008 18:07:00 -0000 [thread overview]
Message-ID: <47DABEE2.70405@qnx.com> (raw)
In-Reply-To: <20080312210431.GA5503@caradoc.them.org>
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...
next prev parent reply other threads:[~2008-03-14 18:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 19:32 Aleksandar Ristovski
2008-03-12 19:18 ` Aleksandar Ristovski
2008-03-12 19:25 ` Vladimir Prus
2008-03-12 19:34 ` Daniel Jacobowitz
2008-03-12 20:49 ` Aleksandar Ristovski
2008-03-12 21:05 ` Daniel Jacobowitz
2008-03-14 18:07 ` Aleksandar Ristovski [this message]
2008-03-21 15:07 ` Daniel Jacobowitz
2008-03-28 15:24 Aleksandar Ristovski
2008-03-28 15:59 ` Daniel Jacobowitz
2008-03-28 16:00 ` Daniel Jacobowitz
2008-03-28 16:16 Aleksandar Ristovski
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=47DABEE2.70405@qnx.com \
--to=aristovski@qnx.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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