This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

pending/1522: A thread has-a selected/current frame


>Number:         1522
>Category:       pending
>Synopsis:       A thread has-a selected/current frame
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   unknown
>Arrival-Date:   Mon Jan 19 20:08:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 Hello,
 
 At present the selected and current frame are maintained as single 
 globals, and independant of the selected and current thread.  As a 
 consequence, each time GDB switches between threads, all global frame 
 state is flushed.
 
 I'm intending to add a "current frame" and "selected frame" to 
 "thread_info" so that, instead this can be maintained on a per-thread basis.
 
 The tricky one is the sentinel-frame.  It needs to be able to perform an 
 arbitrary projection of the virtual thread's register onto the target 
 below's physical threads and memory.   I think this suggests a 
 sentinel-frame parameterized by target, and not just the current regcache.
 
 Thoughts?
 Andrew
 
 
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]