This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/468: cache frame_info in thread_info
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 6 Apr 2002 14:57:45 -0000
- Subject: gdb/468: cache frame_info in thread_info
- Reply-to: ac131313 at redhat dot com
>Number: 468
>Category: gdb
>Synopsis: cache frame_info in thread_info
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Sat Apr 06 06:58:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: ac131313@redhat.com
>Release: 2002-04-05
>Organization:
>Environment:
>Description:
At present there is a single global frame cache. If the selected thread is changed, the cache is discarded.
Instead, have per-thread selected_frame, current_frame (better name?) and just switch between them when the thread changes.
Long term, this should be handled naturally by always using a ``thread'' object. Short term, it can be handled by managing the selected thread's frame using the access methods:
get_current_frame()
+ get_selected_frame()
These functions can track the inferior_tpid vs the one currently selected by the frame.c code.
flush_cached_frames() would iterate over all the threads invalidating all current frames.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: