From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-16958-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 14908 invoked by alias); 5 Nov 2014 18:59:16 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Received: (qmail 14878 invoked by uid 48); 5 Nov 2014 18:59:15 -0000
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: breakpoints
X-Bugzilla-Version: 7.7
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: palves at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-17549-4717-dmyM2kqtI4@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17549-4717@http.sourceware.org/bugzilla/>
References: <bug-17549-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-q4/txt/msg00201.txt.bz2

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.