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

The following reply was made to PR insight/219; it has been noted by GNATS.

From: "Gopal Harikumar" <gharikumar@iname.com>
To: kseitz@sources.redhat.com, gharikumar@iname.com,
  insight-prs@sources.redhat.com, nobody@sources.redhat.com,
  insight-gnats@sources.redhat.com
Cc:  
Subject: Re: insight/219: Insight 5.3:  Classes are not "expandable" in
    the GUI local v ariables window
Date: Wed, 23 Apr 2003 14:05:25 -0500

 Here are the results you wanted. Make check fails
 for some reason, even though the build completed
 fine.
 
 bash-2.05b$ m gdb/gdbtk/ChangeLog
 2002-12-06  Andrew Cagney  <ac131313@redhat.com>
  
         * generic/gdbtk-cmds.c (gdb_update_mem): Don't add a 0x prefix.
  
 bash-2.05b$ m gdb/ChangeLog
 
 2002-12-10  GDB Administrator  <gdbadmin@sourceware.org>
  
         * version.in: Bump to version 5.3.
  
 2002-12-10  Andrew Cagney  <ac131313@redhat.com>
  
         * PROBLEMS: Delete reference to PR gdb/725.
  
         * MAINTAINERS (gdb.c++): Add David Carlton.
 
 
 
 bash-2.05b$ GDB_DISPLAY=:0 make RUNTESTFLAGS="cpp_variable.exp" check
 make do-check NOTPARALLEL=parallel-ok
 make[1]: Entering directory `/opt/haribackups/insight-5.3'
 make[2]: Entering directory `/opt/haribackups/insight-5.3/bfd'
 Making check in doc
 make[3]: Entering directory `/opt/haribackups/insight-5.3/bfd/doc'
 make[3]: Nothing to be done for `check'.
 make[3]: Leaving directory `/opt/haribackups/insight-5.3/bfd/doc'
 Making check in po
 make[3]: Entering directory `/opt/haribackups/insight-5.3/bfd/po'
 make[3]: Nothing to be done for `check'.
 make[3]: Leaving directory `/opt/haribackups/insight-5.3/bfd/po'
 make[3]: Entering directory `/opt/haribackups/insight-5.3/bfd'
 make[3]: Nothing to be done for `check-am'.
 make[3]: Leaving directory `/opt/haribackups/insight-5.3/bfd'
 make[2]: Leaving directory `/opt/haribackups/insight-5.3/bfd'
 make[2]: Entering directory `/opt/haribackups/insight-5.3/etc'
 make[2]: Nothing to be done for `check'.
 make[2]: Leaving directory `/opt/haribackups/insight-5.3/etc'
 make[2]: Entering directory `/opt/haribackups/insight-5.3/intl'
 make[2]: Nothing to be done for `check'.
 make[2]: Leaving directory `/opt/haribackups/insight-5.3/intl'
 make[2]: Entering directory `/opt/haribackups/insight-5.3/itcl'
 for dir in itcl itk iwidgets3.0.0 ; do \
         if test -d $dir ; then \
             echo "$dir: make check" ;\
             if (cd $dir; make check) ; then true ; else exit 1 ; fi ; \
         else \
             exit 1; \
         fi \
 done;
 itcl: make check
 make[3]: Entering directory `/opt/haribackups/insight-5.3/itcl/itcl'
 make[3]: *** No rule to make target `check'.  Stop.
 make[3]: Leaving directory `/opt/haribackups/insight-5.3/itcl/itcl'
 make[2]: *** [check] Error 1
 make[2]: Leaving directory `/opt/haribackups/insight-5.3/itcl'
 make[1]: *** [check-itcl] Error 2
 make[1]: Leaving directory `/opt/haribackups/insight-5.3'
 make: *** [check] Error 2
 
 
 
 
 ----- Original Message -----
 From: kseitz@sources.redhat.com
 Date: 22 Apr 2003 20:44:30 -0000
 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 
 
 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
 
 -- 
 __________________________________________________________
 Sign-up for your own FREE Personalized E-mail at Mail.com
 http://www.mail.com/?sr=signup
 


             reply	other threads:[~2003-04-23 19:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 19:13 Gopal Harikumar [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-22 20:44 kseitz
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=20030423191301.4024.qmail@sources.redhat.com \
    --to=gharikumar@iname.com \
    --cc=insight-prs@sources.redhat.com \
    --cc=kseitz@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).