Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@mvista.com>, "J. Johnston" <jjohnstn@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Pending breakpoints and scripts
Date: Tue, 17 Feb 2004 19:24:00 -0000	[thread overview]
Message-ID: <40326A70.8050601@gnu.org> (raw)
In-Reply-To: <20040211144755.GA487@nevyn.them.org>

> The real problem here is with batch scripts, the change breaks existing 
>> script behavior (which is never a good thing).
>> 
>> How about this, we introduce:
>> 	nquery()
>> 	yquery()
>> where the default (batch mode, and when return is pressed is n/y 
>> respectively).  We'd need the language police to look over the interface 
>> but should otherwize be ok.
> 
> 
> Works for me.

Lets see if we can pin down the interface (adding JeffJ to the CC list):

nquery("A question?")

	A question? [n]:

	- press return => implied "n"
	- batch mode => implied "n"

that would mean here:

> if (!query ("Make breakpoint pending on future shared library load? ")

nquery ("Make breakpoint pending on future shared library load?");

	Make breakpoint pending on future shared library load? [n]:

	- press return => old behavior
	- batch mode => old behavior
	- "y" => new behavior

Looking at the "set breakpoint pending":

yes - implies the above is "y"
no - implies that the above is "n"
auto - implies that the query occures

Jeff, work for you?

Andrew



  reply	other threads:[~2004-02-17 19:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-09 20:02 Andrew Cagney
2004-02-09 22:32 ` Daniel Jacobowitz
2004-02-10 21:22   ` Andrew Cagney
2004-02-10 22:26     ` Daniel Jacobowitz
2004-02-11  3:48       ` System calls debugging MuthuKumar-Hotpop
2004-02-12  9:58         ` how to include subdirectories too, for the source directory murugesan
2004-02-12 13:07           ` Bob Rossi
2004-02-13  4:23             ` murugesan
2004-02-11 14:31       ` Pending breakpoints and scripts Andrew Cagney
2004-02-11 14:47         ` Daniel Jacobowitz
2004-02-17 19:24           ` Andrew Cagney [this message]
2004-02-17 19:31             ` Daniel Jacobowitz
2004-02-17 19:39               ` Andrew Cagney
2004-02-17 19:41                 ` Daniel Jacobowitz
2004-02-17 20:07                   ` Jeff Johnston
2004-02-17 20:14                     ` Andrew Cagney
2004-02-17 20:15                       ` Daniel Jacobowitz
2004-02-17 20:13                   ` Andrew Cagney
2004-02-17 20:15                     ` Daniel Jacobowitz
2004-02-17 20:30                       ` Andrew Cagney
2004-02-17 20:35                         ` Daniel Jacobowitz
2004-02-19 22:42           ` [RFA]: Patch for pending " Jeff Johnston
2004-02-23 15:56             ` Andrew Cagney
2004-02-09 22:27 Pending " Michael Elizabeth Chastain
2004-02-09 22:38 ` Andrew Cagney

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=40326A70.8050601@gnu.org \
    --to=cagney@gnu.org \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=jjohnstn@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