In order to be able to implement some enhancements and bugfixes (like #43066,
#90141) and catch-up with JDI capabilities, we need to add support for new
breakpoint properties into the debugger JPDA API.
These are in particulatar: class filters for ExceptionBreakpoint, instance and
thread filters for FieldBreakpoint, MethodBreakpoint and LineBreakpoint, method
signature for MethodBreakpoint and hit counts for all breakpoint types.
Hit counts are a big bread-and-butter of intermediate debugging.
We should also strive to make converge the native and java bpt dialogs
and having a common count UI would be very beneficial.
Has there been any UI study into their use cases?
For example, why an equals and a greater than?
I'm also curious whatthe user-case for multiple-of
is. I've seen it in MSVC but could never figure where it comes
The hardest things to know with bpt counts is actually what to make the
count be. The use-case is typically as follows:
some NPE or SEGV occurs.
user wants to stop at a bpt the last time before the segv.
user sets the btp count to a very high number and runs the app and gets
the NPE or SEGV. The current bpt count is the desired count.
for this dbx and SunStudio has three things:
A distinction between a bpt limit and a bpt count. The bpt fires when
the count hits the limit.
An artificial "infinity" count limit.
An action that assigns the current count to the count limit.