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/18267] New: Need breakpoint count limit, akin to new tab completion limit


https://sourceware.org/bugzilla/show_bug.cgi?id=18267

            Bug ID: 18267
           Summary: Need breakpoint count limit, akin to new tab
                    completion limit
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: breakpoints
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com

A user did "break foo.h:42" and gdb hung.
The user gave up waiting, but if one waits it turns out there were >12,000
hits.

I think this case is sufficiently equivalent to the tab completion limit issue
we recently addressed, and a similar solution would work.
Also, the fact that ^c didn't work is another bug:
https://sourceware.org/bugzilla/show_bug.cgi?id=18266

Alternatively, IWBN if gdb could print a running tally of how many breakpoints
it has found (and allow the user to ^c). But printing running tallies would
require more effort on the CLI front.

The high order bit is being more user friendly, and for now I think being able
to have a limit suffices.

-- 
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]