public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug cli/13700] should allow CLI to switch thread on event Date: Tue, 04 Nov 2014 15:02:00 -0000 [thread overview] Message-ID: <bug-13700-4717-D5WqTiT87J@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13700-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=13700 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot org --- Comment #5 from Tom Tromey <tromey at sourceware dot org> --- FWIW I ran into this again today doing multi-inferior debugging. The current behavior is quite confusing, given that the mode I'm using is "set a catchpoint and then continue the entire tree of processes". The current behavior would be less confusing if gdb printed a warning: "hey, even though this breakpoint hit in inferor N, you're still looking at thread M." -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2014-11-04 15:02 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 ` [Bug cli/13700] " palves at redhat dot com 2012-02-16 18:09 ` 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 [this message]
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-D5WqTiT87J@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: linkBe 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).