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/1524: A target has-a 1:N threads?


>Number:         1524
>Category:       pending
>Synopsis:       A target has-a 1:N threads?
>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 GDB maintains a thread-db that contains all the "threads" 
 known to GDB.  The list is cross-target.  That is, it can include both 
 LWPs from the lower "process layer" and "threads" from the higher 
 "thread layer".
 
 I think the currently implicit target <-> thread relationship should be 
 made more explicit:
 
 - thread_info should point back at it's target
 - a target should let you iterate over its "threads"
 
 This, I belive, will help clean-up the current tid:pid dance.  A thread 
 would always know its target and hence thread operations would always be 
 applied at the correct level.
 
 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]