From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Star wildcard ranges (e.g., "info thread 2.*")
Date: Thu, 14 Jan 2016 11:39:00 -0000 [thread overview]
Message-ID: <1452771555-23153-1-git-send-email-palves@redhat.com> (raw)
In v2:
- Address Eli's documentation review.
- Fix "thread apply" crash in patch #1.
- remove 'state->string = "-"' hack in patch #2.
This series adds support for specifying "all threads of inferior N",
by writing "*" as thread number/range in thread ID lists.
E.g., "info threads 2.*" or "thread apply 2.* bt".
While doing this, I noticed a few bugs in "thread apply" (that even
predate the per-inferior thread IDs series). Patch 1 fixes them. I'm
only keeping both patches together to make it clear that patch 2
applies on top of patch 1.
Pedro Alves (2):
Fix "thread apply $conv_var" and misc other related problems
Star wildcard ranges (e.g., "info thread 2.*")
gdb/NEWS | 6 ++
gdb/cli/cli-utils.c | 47 ++++++++-----
gdb/cli/cli-utils.h | 8 +++
gdb/doc/gdb.texinfo | 39 ++++++++---
gdb/testsuite/gdb.multi/tids.exp | 143 +++++++++++++++++++++++++++++++++++----
gdb/thread.c | 39 ++++++++++-
gdb/tid-parse.c | 63 ++++++++++++++---
gdb/tid-parse.h | 7 ++
8 files changed, 301 insertions(+), 51 deletions(-)
--
1.9.3
next reply other threads:[~2016-01-14 11:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 11:39 Pedro Alves [this message]
2016-01-14 11:39 ` [PATCH 2/2] " Pedro Alves
2016-01-14 11:39 ` [PATCH 1/2] Fix "thread apply $conv_var" and misc other related problems Pedro Alves
-- strict thread matches above, loose matches on Subject: below --
2016-01-13 16:34 [PATCH 0/2] Star wildcard ranges (e.g., "info thread 2.*") Pedro Alves
2016-01-13 16:34 ` Pedro Alves
2016-01-13 16:42 ` Pedro Alves
2016-01-14 16:52 ` Simon Marchi
2016-01-15 21:50 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1452771555-23153-1-git-send-email-palves@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).