From: Jim Ingham <jingham@apple.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Nother little one, this time in varobj.c
Date: Wed, 10 Apr 2002 11:07:00 -0000 [thread overview]
Message-ID: <D85CBC6A-4CAD-11D6-B08E-000393540DDC@apple.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0204092335270.2411-100000@cse.cygnus.com>
Keith,
Yeah, I added the ability to make the frames change (Syd thought that
variables in the watch window should re-evaluate themselves every time
that you changed the stack frame in the debugger - apparently that's
what VC++ does). But I added all this on 03-2000, and the
reinit_frame_cache is already there in the initial import into
sourceware. Unfortunately, the sourceware repository history only goes
back to Feb. 2000, and this was all checked in before that. If you can
look in the cygnus repository, you might at least be able to figure out
who should remember why this is there - not that this actually helps
that much...
Jim
On Tuesday, April 9, 2002, at 11:37 PM, Keith Seitz wrote:
> On Tue, 9 Apr 2002, Jim Ingham wrote:
>
>> BTW, I am not sure why it is necessary to call reinit_frame_cache here.
>> Keith, do you remember why this was necessary? It is inefficient,
>> especially if you are evaluating a bunch of variables that are fairly
>> high up on the stack. But since I don't remember why this was done, I
>> am reluctant to just change it outright...
>
> I haven't a clue, actually. When I originally wrote varobj for Insight,
> it
> did not allow varobjs to change frames dynamically, as it does now.
> Presumably, this was all added at the same time. (Or I've forgotten all
> about it...)
>
> Keith
>
>
>
--
Jim Ingham jingham@apple.com
Developer Tools - gdb
Apple Computer
prev parent reply other threads:[~2002-04-10 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 17:36 Jim Ingham
2002-04-09 23:44 ` Keith Seitz
2002-04-10 6:27 ` Fernando Nasser
2002-04-10 7:33 ` Andrew Cagney
2002-04-10 11:07 ` Jim Ingham [this message]
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=D85CBC6A-4CAD-11D6-B08E-000393540DDC@apple.com \
--to=jingham@apple.com \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@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