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]

breakpoints/2428: add a way to toggle breakpoint 'silent' status


>Number:         2428
>Category:       breakpoints
>Synopsis:       add a way to toggle breakpoint 'silent' status
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Mar 10 01:08:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Tom Tromey <tromey@redhat.com>
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
When specifying breakpoint commands I often forget
the initial "silent".  It would be convenient to have
a way to change this setting after the fact.

I had a couple ideas for how to do this -- neither ideal.

First, make "silent" a real command.  It could work like:
  silent [-no] breakpoint-list
I am not overly fond of "-no", but adding a new "verbose"
command doesn't seem great.

Second, add options to "commands".
  commands [-silent | -verbose] breakpoint-list
If given -silent/-verbose, it would not prompt for
further commands.  I somewhat prefer this.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]