Too many breakpoints message not valid for Full Debugging.

[Justin Julicher]

If you have more than 5 break points set it displays the message too many breakpoints.

However, when you use the full debugger you can set as many break points as you like so the message is pointless in that context.

Can it be disabled?

[Scott Wells]

Justin, when you say "full debugger", what do you mean?

One of the issues here is that you can have checkpoints which are executed on the server, and there is a max of five for those, and you can have breakpoints which tell the debugger to stop in IC2. Right now the two are conflated, and the properties for an offline debugger breakpoint default to "Dump Heap" which make that breakpoint into a checkpoint. I've been wanting to separate those two so that you can set one or the other, and only checkpoints would be limited in quantity. Is that perhaps what you're referencing?

[Scott Wells]

Just committed a change for the next build to have distinct notions of local breakpoints which can exist in any quantity and server checkpoints (heap dumps, action scripts, etc.) for which only five are allowed against a given org:

[Justin Julicher]

Scott that is awesome!

thanks

[Scott Wells]

Delivered in 2.1.6.4.