public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/13700] should allow CLI to switch thread on event
Date: Thu, 16 Feb 2012 15:15:00 -0000	[thread overview]
Message-ID: <bug-13700-4717-5n1uvGYFvw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13700-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=13700

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |palves at redhat dot com

--- Comment #1 from Pedro Alves <palves at redhat dot com> 2012-02-16 15:13:17 UTC ---
I remembered why I never looked back at this.
It is not clear to me we should always do that.

Consider:

 (gdb) next
 * other random thread stops*
 [switched to $random_thread]
 (gdb) foofoo
 * next finishes later *
 (gdb) foofoofoofoo

I think the user may want to stay focused on the "next" instead of
being distracted by the other stop.

Switching focus on "continue" only would be my next idea, but,
I'm still not sure.  The user may "break foo; continue"; and expect
the foo breakpoint to hit, instead of being distracted by other
threads.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  reply	other threads:[~2012-02-16 15:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 14:51 [Bug cli/13700] New: " tromey at redhat dot com
2012-02-16 15:15 ` palves at redhat dot com [this message]
2012-02-16 18:09 ` [Bug cli/13700] " tromey at redhat dot com
2012-02-16 18:30 ` palves at redhat dot com
2012-02-20 19:11 ` palves at redhat dot com
2014-11-04 15:02 ` 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-13700-4717-5n1uvGYFvw@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).