From: nickrob@snap.net.nz (Nick Roberts)
To: Daniel Jacobowitz <drow@false.org>
Cc: Marc Khouzam <marc.khouzam@ericsson.com>, gdb@sourceware.org
Subject: Re: [RFC] Queries and frontends
Date: Tue, 21 Jul 2009 23:29:00 -0000 [thread overview]
Message-ID: <19046.20305.111007.76142@totara.tehura.co.nz> (raw)
In-Reply-To: <20090721185508.GA16411@caradoc.them.org>
Daniel Jacobowitz writes:
> On Tue, Jul 21, 2009 at 02:36:38PM -0400, Marc Khouzam wrote:
> > I guess it's just me then.
> > But with "set confirm off", which one may choose to use, how
> > would you set pending breakpoints, currently?
> > You just won't be able to, right? Isn't that a problem?
>
> In fact:
>
> (gdb) show breakpoint pending
> Debugger's behavior regarding pending breakpoints is auto.
GDB never prompts with pending breakpoints in GDB/MI because it temporarly
sets deprecated_query_hook:
deprecated_query_hook = mi_interp_query_hook
In any case I'm not concerned about all queries: if they're issued from the
GUD buffer Emacs currently handles them fine. I just need to avoid them for
those GDB commands which are run behind the users back.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2009-07-21 23:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 3:18 Marc Khouzam
2009-07-21 6:13 ` Nick Roberts
2009-07-21 8:26 ` Hui Zhu
2009-07-21 8:29 ` Hui Zhu
2009-07-21 11:51 ` Nick Roberts
2009-07-22 6:11 ` Hui Zhu
2009-07-21 17:57 ` Michael Snyder
2009-07-21 18:37 ` Marc Khouzam
2009-07-21 18:55 ` Daniel Jacobowitz
2009-07-21 23:29 ` Nick Roberts [this message]
2009-07-22 13:38 ` Marc Khouzam
2009-07-26 5:04 ` Tom Tromey
2009-07-27 1:52 ` Nick Roberts
2009-07-27 16:17 ` Tom Tromey
2009-07-28 1:55 ` Nick Roberts
2009-07-29 21:13 ` Tom Tromey
2009-07-29 23:56 ` [PATCH] util.c + doc [was Re: [RFC] Queries and frontends] Nick Roberts
2009-07-30 0:28 ` Marc Khouzam
2009-07-30 3:13 ` Eli Zaretskii
2009-08-04 16:32 ` [PATCH] util.c + doc Tom Tromey
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=19046.20305.111007.76142@totara.tehura.co.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.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