public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: kseitz@sources.redhat.com
To: gharikumar@iname.com, insight-prs@sources.redhat.com,
	kseitz@sources.redhat.com, nobody@sources.redhat.com
Subject: Re: insight/219: Insight 5.3:  Classes are not "expandable" in the GUI local v ariables window
Date: Tue, 22 Apr 2003 20:44:00 -0000	[thread overview]
Message-ID: <20030422204430.7316.qmail@sources.redhat.com> (raw)

Synopsis: Insight 5.3:  Classes are not "expandable" in the GUI local v ariables window

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Tue Apr 22 20:44:30 2003
Responsible-Changed-Why:
    mine
State-Changed-From-To: open->analyzed
State-Changed-By: kseitz
State-Changed-When: Tue Apr 22 20:44:30 2003
State-Changed-Why:
    The testsuite checks this. I just updated from the 5.3 branch and I am not seeing any problems with the test "cpp_variable.exp". If you "cd" to your gdb build directory, you can run this by typing:
    
    GDB_DISPLAY=:0 make RUNTESTFLAGS="cpp_variable.exp" check
    
    You can omit GDB_DISPLAY if you have Xvfb installed. You can also run insight on the executable that is output by the testsuite. It will be in testsuite/gdb.gdbtk/cpp_variable. Can you check if this works?
    
    Lastly, what is the newest ChangeLog entry in gdb/gdbtk/ChangeLog? Ditto for gdb/ChangeLog.

http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=219


             reply	other threads:[~2003-04-22 20:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 20:44 kseitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-19 21:39 kseitz
2003-04-24 15:23 Keith Seitz
2003-04-23 19:43 Keith Seitz
2003-04-23 19:33 Keith Seitz
2003-04-23 19:23 Keith Seitz
2003-04-23 19:13 Gopal Harikumar
2003-04-11  1:53 gharikumar

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=20030422204430.7316.qmail@sources.redhat.com \
    --to=kseitz@sources.redhat.com \
    --cc=gharikumar@iname.com \
    --cc=insight-gnats@sources.redhat.com \
    --cc=insight-prs@sources.redhat.com \
    --cc=nobody@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).