On Saturday 19 February 2011 18:01:44, msnyder@sonic.net wrote:
This will break printing internal breakpoints, which are negative.
AFAIK, "info break" never supported printing internal breakpoints.
That's what "maint info break" is for.
Sorry, I misread and though you were changing breakpoint_1, which
is the backend for "info break", "maint info break", etc.
Doesn't this patch have the same problem I pointed out with
"info threads 1-100", in that you'll print the header once
for each breakpoint in the range?