This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/467: cache fetched register value/addr/opt in frame_info
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 6 Apr 2002 14:52:27 -0000
- Subject: gdb/467: cache fetched register value/addr/opt in frame_info
- Reply-to: ac131313 at redhat dot com
>Number: 467
>Category: gdb
>Synopsis: cache fetched register value/addr/opt in frame_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:
GDB caches registers in the regcache. GDB doesn't cache [per-thread] saved registers found on the stack or computed.
Suggest modifying get_saved_register() (?) so that it it caches register value/addr/... in the frame obstack. Later register reads can fetch the value from that cache instead of from the target.
If target registers or memory are changed the cache and the entire frame would need to be flushed (but this is already the case).
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: