From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25858 invoked by alias); 8 Feb 2014 03:18:59 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 25846 invoked by uid 89); 8 Feb 2014 03:18:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Sat, 08 Feb 2014 03:18:57 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 2D3381162B5; Fri, 7 Feb 2014 22:18:56 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9ahiQVAxHmns; Fri, 7 Feb 2014 22:18:56 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 962FE1162B2; Fri, 7 Feb 2014 22:18:55 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 2BDCBE0BA8; Sat, 8 Feb 2014 07:18:54 +0400 (RET) Date: Sat, 08 Feb 2014 03:18:00 -0000 From: Joel Brobecker To: andre Cc: Yao Qi , gdb-patches@sourceware.org Subject: Re: [PATCH] Test no =breakpoint-modified is emitted for modifications from MI commands Message-ID: <20140208031854.GM5485@adacore.com> References: <1390549587-23625-1-git-send-email-yao@codesourcery.com> <52F381B0.4010602@codesourcery.com> <20140206203936.GA7055@klara.mpi.htwm.de> <52F4A366.6060704@codesourcery.com> <20140207161221.GA5150@klara.mpi.htwm.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140207161221.GA5150@klara.mpi.htwm.de> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2014-02/txt/msg00236.txt.bz2 > > > - prevent the user from entering MI commands in the console > > > (and try to catch all possible workarounds to sneak in MI > > > commands nevertheless), [...] > > #1 is fine to me. > > But not for me. I don't want to needlessly restrict what my users are > allowed to type, or not. It might even e.g. be useful to copy/paste/modify > previously sent MI commands and send them manually via the console. In your > approach this would not be possible, or at least require the user to > re-write the full command in non-MI syntax. I don't feel strongly about it, but I kind of see Andre's point. If we can allow a certain type of usage without damaging consequences for the rest of the operations, why not? Wouldn't it simplify the notification mechanism too? Food for thought: I think it would be interesting to investigate whether FEs would notice if they started receiving those extra notifications. I hope the processing would be fast enough that they wouldn't. One other possible option: Add a new option that would be available to all commands to disable notifications related to the command being executed. That way, FE could use it to reduce unnecessary back-chatter. I don't really like that option, though, as it would require a certain transition period. -- Joel