From: Keith Seitz <keiths@redhat.com>
To: Gopal Harikumar <gharikumar@iname.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>,
insight-gnats@sources.redhat.com
Subject: Re: insight/219: Insight 5.3: Classes are not "expandable" in the GUI local v ariables window
Date: Thu, 24 Apr 2003 15:20:00 -0000 [thread overview]
Message-ID: <1051197731.1534.2.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <20030424013821.36746.qmail@iname.com>
On Wed, 2003-04-23 at 18:38, Gopal Harikumar wrote:
> I just confirmed that the problem exists even
> in the latest snapshot
>
> insight+dejagnu-5.3.0.90_20030421.tar.bz2
I've downloaded the "5.3.0.90_20030422.tar.bz2" (I couldn't find one
dated 0421), and ran the tests and double-checked them by hand. Those
tests work.
I'm afraid we've got two choices left:
1) Try a CVS version/snapshot (which should be much faster and contains
lots of other bug fixes)
2) Send me a testcase
Keith
next prev parent reply other threads:[~2003-04-24 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 1:38 Gopal Harikumar
2003-04-24 15:20 ` Keith Seitz [this message]
[not found] <20030423205040.43533.qmail@iname.com>
2003-04-23 21:04 ` Keith Seitz
2003-04-24 1:11 ` Andrew Cagney
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=1051197731.1534.2.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=gharikumar@iname.com \
--cc=insight-gnats@sources.redhat.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).