public inbox for
help / color / mirror / Atom feed
From: Keith Seitz <>
Subject: Re: insight/219: Insight 5.3:  Classes are not "expandable" in the GUI local v ariables window
Date: Wed, 23 Apr 2003 19:33:00 -0000	[thread overview]
Message-ID: <> (raw)

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

From: Keith Seitz <>
Subject: Re: insight/219: Insight 5.3:  Classes are not "expandable" in the
	GUI local v ariables window
Date: 23 Apr 2003 12:32:40 -0700

 On Wed, 2003-04-23 at 12:23, Keith Seitz wrote:
 >  On Wed, 2003-04-23 at 12:05, Gopal Harikumar wrote:
 >  > bash-2.05b$ m gdb/gdbtk/ChangeLog
 >  > 2002-12-06  Andrew Cagney  <>
 >  >  
 >  >         * generic/gdbtk-cmds.c (gdb_update_mem): Don't add a 0x prefix.
 >  Zowie! I just updated from the branch... There are a TON of updates for
 >  both gdb and Insight. I suggest grabbing a newer 5.3 release. I have
 >  ChangeLog entries that are as new as 2002-07 for gdb and 2002-03 for
 >  Insight. You're certainly missing a giant varobj patch that I committed
 >  on 2002-01-13.
 Hmmm. Which branch did you check out? Turns out that I've not been using
 gdb_5_3-branch. I've actually been testing on gdb_5_2-branch. Sorry.
 (Did I really say that you're missing an update from 2002-01??? Sorry, I
 must be losing my mind!)
 I'm building the real 5.3 branch now. Stay tuned.

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 19:33 Keith Seitz [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:23 Keith Seitz
2003-04-23 19:13 Gopal Harikumar
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).