This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Re: RFC: Frame cache s not always available.
- To: gdb-patches at sourceware dot cygnus dot com
- Subject: Re: RFC: Frame cache s not always available.
- From: Jim Kingdon <kingdon at redhat dot com>
- Date: 26 Feb 2000 11:46:53 -0800
- Newsgroups: cygnus.patches.gdb
- Organization: Cygnus Solutions
- References: <38B40EB5.E9503E1C@redhat.com>
> For some oversighting, or maybe because it is gradually being
> implemented, gdb only tests for the return value of
> get_current_frame() in one place and assumes in several places that
> selected_frame is set.
I think it is the "gradually being implemented" thing (whether
deliberate or not). There are a lot of things which want frames (in
various subtle ways) and so it is going to take a while to get the
code dealing with the lack of frames.
Of course, in cases like multi-threading, in which the frames are
actually out there, it will presumably be better to set up the frames,
rather than deal with them being missing. Even low-level stuff like
stepping depends on the frames (for whether to step into a function
and such).
> I found two places that are more troublesome and created the attached
> patch.
I don't see problems with this patch, except that I think I'd change
"No stack." to "No frames.". The former could be pretty confusing
since it also means things like "there is no memory which GDB knows
about".