Michael Snyder wrote: > Eli Zaretskii wrote: >>> Date: Fri, 11 Feb 2011 16:32:54 -0800 >>> From: Michael Snyder >>> CC: "gdb-patches@sourceware.org" >>> >>> Pedro Alves wrote: >>>> On Friday 11 February 2011 22:12:39, Michael Snyder wrote: >>>>> This is purposefully rough, 'cause I hope for discussion. >>>>> >>>>> This is a new command to help manage large thread lists. >>>>> I started with the idea "I want to find out which thread >>>>> has target id 12345", then extended it to also handle the >>>>> new concept of thread names (which thread has name 'foo'), >>>>> and extra info as well (which thread has extra info that >>>>> includes the string "xyz"). >>>>> >>>>> The syntax (I'm open to renaming etc.): >>>>> >>>>> thread tid [NAME | TARGET_ID | EXTRA_INFO] >>>> Shouldn't this be under "info" or "show"? >>> Suits me, but >>> 1) I'd prefer it wasn't "show", because there is no "set". >>> 2) Info what? tid? thread-id? >> thread show [NAME | TARGET_ID | EXTRA_INFO] >> thread info [NAME | TARGET_ID | EXTRA_INFO] > > How about "thread find"? Here's a new diff combining both patches (since they sort of relate), and implementing some of your suggestions. * info thread can now take a list of thread ids (closer to a thread set) * thread find (so called) can now take a regular expression. Tom, since you implemented the thread name, I'd like to know if this scheme fits in with what you had in mind.