Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jeff Johnston <jjohnstn@redhat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC]: new set breakpoint pending and show breakpoint pending commands
Date: Thu, 26 Feb 2004 23:47:00 -0000	[thread overview]
Message-ID: <403E859D.9020902@redhat.com> (raw)
In-Reply-To: <403E5603.6010203@gnu.org>

Andrew Cagney wrote:
>> Double Ping ...
> 
> 
> Thought I'd covered it, sorry.  Yes, ok (and finally some more sanity in 
> GDB's cli structure!)
> 
> Can you create a breakpoint bug report to move all the other breakpoint 
> options into "set/show breakpoint".
> 
> Andrew
> 

Done.  See gdb/1575.  Patch checked in.  Thanks.

-- Jeff J.

>> Jeff Johnston wrote:
>>
>>> Ping...[excluding Eli who graciously reviewed the doc change]
>>>
>>> Jeff Johnston wrote:
>>>
>>>> The following patch adds a setting to control how gdb creates 
>>>> pending breakpoints.  At Andrew's suggestion, I have made the 
>>>> setting a subsetting of breakpoint so future breakpoint settings 
>>>> will all be grouped together.
>>>>
>>>> The setting is an auto boolean and has three settings: on, off, and 
>>>> auto.  The default behavior is auto which is the current default 
>>>> behavior of querying before setting a pending breakpoint.  The on 
>>>> setting causes pending breakpoints to be created automatically 
>>>> without prompting and the off setting causes no pending breakpoints 
>>>> to be created.  The off setting causes an error to occur which 
>>>> matches the previous behavior Andrew was seeing with regard to scripts.
>>>>
>>>> I have included a doc patch but will wait on posting a change to 
>>>> pending.exp until everyone is ok with the interface.  A change is 
>>>> not required to make pending.exp work, it would just exercise the 
>>>> new functionality.  I have tested the new settings manually.
>>>>
>>>> Ok?
>>>>
>>>> -- Jeff J.
>>>>
>>>> gdb/ChangeLog:
>>>>
>>>> 2004-02-10  Jeff Johnston  <jjohnstn@redhat.com>
>>>>
>>>>         * breakpoint.c (pending_break_support): New setting variable.
>>>>         (break_command_1): Account for pending_break_support setting
>>>>         when creating pending breakpoints.
>>>>         (set_breakpoint_cmd, show_breakpoint_cmd): New functions.
>>>>         (_initialize_breakpoint): Add "set breakpoint pending" and
>>>>         "show breakpoint pending" commands.
>>>>
>>>> doc/ChangeLog:
>>>>
>>>> 2004-02-10  Jeff Johnston  <jjohnstn@redhat.com>
>>>>
>>>>         * gdb.texinfo (breakpoints): Add information about the
>>>>         new "set breakpoint pending" and "show breakpoint pending"
>>>>         commands.
>>>>
>>>>
> 
> 


      reply	other threads:[~2004-02-26 23:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-11  0:18 Jeff Johnston
2004-02-11  6:19 ` Eli Zaretskii
2004-02-11 22:10   ` Jeff Johnston
2004-02-19 22:38 ` Jeff Johnston
2004-02-26 20:06   ` Jeff Johnston
2004-02-26 20:24     ` Andrew Cagney
2004-02-26 23:47       ` Jeff Johnston [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=403E859D.9020902@redhat.com \
    --to=jjohnstn@redhat.com \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox