public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jimmy Guo <guo@cup.hp.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sourceware.cygnus.com,
	"Insight (GDB GUI)" <insight@sourceware.cygnus.com>
Subject: Re: gdb.gdbtk tests
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.10.10003231557490.9146-100000@hpcll168.cup.hp.com> (raw)
Message-ID: <20000401000000.L2qVm66sXtrowNDyJPe_hPEQlqifP_2qgMG9KMafsGM@z> (raw)
In-Reply-To: <38DAA014.780BE4BD@cygnus.com>

>They are already available.  Either download the insight+dejagnu
>snapshot or checkout the module ``insight''.

Oh, I only extract gdb + dejagnu.

>The ``GDB'' module doesn't include the gdb.gdbtk testsuites.  However,
>given that it's pretty easy to end up with that directory, a more robust
>test would be better.

I don't know if there's any easy way to maintain the modules aliases to
separate out the gdb.gdbtk test suite from mainline gdb tree.  As of
3/21 that's not the case (or I wouldn't see the test suite).  Keeping it
in the tree would be fine provided that a better bypass than the current
(let TCL complain about 'cd' failure and dump call trace).  For now,
locally, I'm adding gdb.gdbtk to the skip list in site.exp.

- Jimmy

  reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-23 11:53 Jimmy Guo
2000-03-23 14:56 ` Andrew Cagney
2000-03-23 15:02   ` Jimmy Guo [this message]
2000-03-23 16:50     ` Andrew Cagney
2000-04-01  0:00       ` Andrew Cagney
2000-04-01  0:00     ` Jimmy Guo
2000-04-01  0:00   ` Andrew Cagney
2000-04-01  0:00 ` Jimmy Guo

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=Pine.LNX.4.10.10003231557490.9146-100000@hpcll168.cup.hp.com \
    --to=guo@cup.hp.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=insight@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).