This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug breakpoints/17549] catch load seems to be inferior-specific


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]