Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: FYI: fixlet for linux-dp.exp
Date: Thu, 26 Apr 2012 14:43:00 -0000	[thread overview]
Message-ID: <87ty068sgz.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4F9955CD.5040106@redhat.com> (Pedro Alves's message of "Thu, 26	Apr 2012 15:03:57 +0100")

>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:

Pedro> I assume this would mean use "interp create".  It's even on
Pedro> dejagnu's TODO file:

Yeah.  Or possibly just with "namespace", but I think that may be harder.

Pedro> I think the trouble would be globals that _are_ supposed to be persistent
Pedro> across tests, like e.g., "portnum", or whatever other globals board
Pedro> files can come up with.  We'd need some common way to make
Pedro> those "master interp" owned variables (through aliases or env vars?).
Pedro> Alternatively, we could save/restore globals, but there's no globals
Pedro> standard naming scheme in place to make that remotely sane.

Yes, for "advertised" globals we'd have to make aliases and arrange for
them to be shared.

But, the idea is to avoid odd problems like the one I hit, where test
ordering can cause errors due to minor clashes from the choice of
local-to-the-.exp variable names.

In the end it is probably simpler to just fix our tests when random
issues crop up, than it is to try to fix dejagnu.  Plus maybe we could
use namespaces more in our own tests or something like that.

Tom


      parent reply	other threads:[~2012-04-26 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25 14:39 Tom Tromey
2012-04-26 14:04 ` Pedro Alves
2012-04-26 14:34   ` Joel Brobecker
2012-04-26 14:43   ` Tom Tromey [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=87ty068sgz.fsf@fleche.redhat.com \
    --to=tromey@redhat.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