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/9532] let "commands" select more than one breakpoint


------- Additional Comments From mnemo at minimum dot se  2009-08-14 19:24 -------
As described in bug 10523, it's intuitive that a plain "commands" invocation
done right after executing "rbreak" should apply those "commands" to all the
breakpoints created by the previous "rbreak". I still think it should be many
breakpoints though because after rbreak/commands you might want to remove one or
two of them or disable some of them etc.

A simple use case is: user is trying to understand a new code base, he
specifically wants to understand how a certain class interacts with the rest of
the program. Thus he types:

rbreak SomeClass::*
commands
silent
bt 8
c
end

The existing behavior of letting a plain "commands" affect only the last
breakpoint setup by "rbreak" is not really that useful.

-- 


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


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