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 breakpoints/17549] catch load seems to be inferior-specific
Date: Wed, 05 Nov 2014 18:59:00 -0000	[thread overview]
Message-ID: <bug-17549-4717-dmyM2kqtI4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17549-4717@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Pedro Alves <palves at redhat dot com> ---
I meant, by default.  I can certainly see how one may want to restrict a
catchpoint to an inferior, but I think that by default, a catchpoint should
trigger in all inferiors, like breakpoints.

I think restricting breakpoints to an inferior by default is more confusing and
surprising to users; users naturally miss/forget this, as evidenced by this PR.
 Bug 13457 shows another example that's easy to miss.

Then if the user wants to restrict it to some inferior, thread, etc., then she
should be able to do that, ideally with itsets (which I've been working on --
all the recent-ish run control fixes are preparatory work for
all-stop-on-non-stop, which is a prerequisite for itsets).

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


      parent reply	other threads:[~2014-11-05 18:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 16:14 [Bug breakpoints/17549] New: " tromey at sourceware dot org
2014-11-04 17:10 ` [Bug breakpoints/17549] " palves at redhat dot com
2014-11-05  7:51 ` xdje42 at gmail dot com
2014-11-05 18:59 ` palves at redhat dot com [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-17549-4717-dmyM2kqtI4@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).