public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "moshe.rubin at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/30771] GDB needs a silent thread-selecting command akin to "select-frame"
Date: Wed, 16 Aug 2023 18:15:01 +0000	[thread overview]
Message-ID: <bug-30771-4717-RuWyfbOAle@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30771-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30771

--- Comment #2 from Moshe Rubin <moshe.rubin at gmail dot com> ---
Thanks or your prompt reply <g>.  I see that "pipe" was introduced in gdb 9.1. 
My company currently uses version 8.2.1 across the organization.  You can
imagine that IT's changing this will take time.

Your suggestion to use pipe is an interesting one and would answer the
immediate need.  I look forward to my organization upgrading to GDB 9.1.  I do
think, however, that having "select-thread" as a parallel to "select-frame" is
logical and makes the Python code clearer and better understood.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-08-16 18:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16 15:41 [Bug gdb/30771] New: GDB need " moshe.rubin at gmail dot com
2023-08-16 17:37 ` [Bug cli/30771] " tromey at sourceware dot org
2023-08-16 17:58 ` [Bug cli/30771] GDB needs " moshe.rubin at gmail dot com
2023-08-16 18:15 ` moshe.rubin at gmail dot com [this message]
2023-08-16 22:27 ` tromey at sourceware dot org
2023-08-17  7:20 ` moshe.rubin at gmail dot com
2023-08-17 13:00 ` tromey at sourceware dot org
2023-08-18 12:08 ` moshe.rubin at gmail dot com
2024-05-08 18:47 ` tromey at sourceware dot org

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=bug-30771-4717-RuWyfbOAle@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).