This is the mail archive of the gdb-patches@sources.redhat.com 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] |
Date: Thu, 9 Oct 2003 10:08:48 -0400From: Daniel Jacobowitz <drow@mvista.com>
From a user interface perspective, I got a really strong negative pushback the last time I tried to add a switch to any GDB command.
Any pointers to messages where such pushback could be seen? I'm curious what could be the motivation.
(gdb) info break --l (gdb) info break -l
Another possibility would be to have 2 commands: "info breakpoints" which only shows one breakpoint for each user breakpoint, and "info all-breakpoints", which shows all of them. We already have a precedent for such an arrangement with "info registers" vs "info all-registers".
Anyway, going to the maint-land is something I think we should avoid in this case, as the breakpoints not shown by default are interesting not only for GDB maintainers.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |