Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Fix DOS clash with mi0-var-*.exp
Date: Fri, 29 Jun 2001 08:31:00 -0000	[thread overview]
Message-ID: <3B3C9491.5020500@cygnus.com> (raw)
In-Reply-To: <3791-Fri29Jun2001102809+0300-eliz@is.elta.co.il>

> Date: Thu, 28 Jun 2001 15:23:31 -0400
>> From: Andrew Cagney <ac131313@cygnus.com>
>> 
>> The attatched patch addresses a DOS file name clash caused by all the 
>> mi0-var-*.exp files I recently created.
>> 
>> Is this the correct way to do this?  The files aren't used in a DOS build.
> 
> 
> Yes, this is the way.  However:
> 
> 
>> + @V@/gdb/testsuite/gdb.mi/mi0-var-cmd.exp @V@/gdb/testsuite/gdb.mi/mi0-varcmd.exp
>> + @V@/gdb/testsuite/gdb.mi/mi0-var-child.exp @V@/gdb/testsuite/gdb.mi/mi0-varchild.exp
> 
> 
> These two still clash: truncation to 8+3 yields "mi0-varc.exp" for
> both of them.


Will fix.

Hmm, that would mean that mi-var-cmd.exp and mi-var-child.exp also 
clash.  Ah, yes found them hidden in fnchange.lst, would you object to 
me (separatly) sorting that file?


> Actually, I wonder why do we have to keep those mi0- prefixes.  This
> is all in gdb.mi subdirectory, so there should be no need to stress
> the fact we are talking about mi.  If the zero is significant, we can
> keep it, but "mi" can go, I think.


If my memory is correct, it is a namespace proof things.  While it looks 
like a two level structure dejagnu ignores this and just worries about 
the basename.  If I tell dejagnu to run the test ``var-cmd.exp'' I get 
all of them.

	Andrew


  reply	other threads:[~2001-06-29  8:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3B3B8433.7020300@cygnus.com>
2001-06-29  0:31 ` Eli Zaretskii
2001-06-29  8:31   ` Andrew Cagney [this message]
2001-06-29  8:57     ` Eli Zaretskii
2001-06-29  9:18       ` Andrew Cagney
2001-07-09 13:52     ` Fernando Nasser

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=3B3C9491.5020500@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --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