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]

mi/1513: Extract the thread name


>Number:         1513
>Category:       mi
>Synopsis:       Extract the thread name
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed Jan 14 18:58:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     alain@qnx.com
>Release:        GDB-6.x
>Organization:
>Environment:
Any environment
>Description:
>From a discussion on the CDT Debug mailing list,
It would be nice to be able to retrieve the Thread name
part of mi, for now -thread-list-ids does not give the
information nor it gives the current thread.

> >
> > The way we determine native thread names in GDB is by using the "info threads" GDB
> > command implemented in a custom GDB remote target connection. I believe that this
> > approach is quite common in the embedded world. On Solaris, the "info threads" GDB
> > command reports the Solaris LWP id. I don't remember what OS information "info
> > threads" reports on Linux and Windows.
> >
> 
> The problem, how do you get, in a portable way, the name of a thread in gdb.
> 
> 1) GDB/MI:
> 
>      -thread-list-ids
>      ^done,thread-ids={thread-id="3",thread-id="2",thread-id="1"}, number-of-threads="3"
> 
> If this command could be enhance to provide, current selected thread and thread names,
> that would be perfect.
                                                                                                                             
>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]