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/1523: "there is always a thread"


>Number:         1523
>Category:       pending
>Synopsis:       "there is always a thread"
>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:
 To re-ping an old topic.
 
 At present GDB differentiates between a "non-threaded" and "threaded" 
 inferior.  It only creates the thread data structures when there are 
 threads.
 
 I'm intending simplifying this so that the code can assume that there's 
 always a "thread".  A non-threaded app having a single thread 
 corresponding to the main process.
 
 enjoy,
 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]