This is the mail archive of the gdb-patches@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]

Re: [RFA] set debug mi

From: Michael Snyder <Michael dot Snyder at access-company dot com>
To: Nick Roberts <nickrob at snap dot net dot nz>
Cc: gdb-patches at sources dot redhat dot com
Date: Wed, 11 Apr 2007 17:53:50 -0700
Subject: Re: [RFA] set debug mi
References: <1176335457.26620.48.camel@svmsnyderlnx.palmsource.com> <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.

References:
- [RFA] set debug mi
  - From: Michael Snyder
- Re: [RFA] set debug mi
  - From: Nick Roberts

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