From: Michael Snyder <Michael.Snyder@access-company.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] set debug mi
Date: Thu, 12 Apr 2007 00:53:00 -0000 [thread overview]
Message-ID: <1176339230.26620.58.camel@svmsnyderlnx.palmsource.com> (raw)
In-Reply-To: <17949.32037.351459.701252@farnswood.snap.net.nz>
On Thu, 2007-04-12 at 12:28 +1200, Nick Roberts wrote:
> > Anybody think this is useful?
>
> Maybe. I'll take a look. Have you used it? Would it be better to register
> it as an MI command so that the user doesn't inadvertantly turn it on? I guess
> that the output would confuse any front end.
So far I've used it only in the process of implementing it,
but I implemented it because I plan to use it.
As far as inadvertant activation etc., I look at it as
analogous to the "set debug remote" command. Perhaps both
should be made "maintainer" commands.
next prev parent reply other threads:[~2007-04-12 0:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 23:51 Michael Snyder
2007-04-12 0:31 ` Nick Roberts
2007-04-12 0:53 ` Michael Snyder [this message]
2007-04-12 0:42 ` Jason Molenda
2007-04-12 0:51 ` Michael Snyder
2007-04-12 6:40 ` Vladimir Prus
2007-04-12 15:34 ` Daniel Jacobowitz
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=1176339230.26620.58.camel@svmsnyderlnx.palmsource.com \
--to=michael.snyder@access-company.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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