From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3419 invoked by alias); 27 Jul 2012 17:07:17 -0000 Received: (qmail 3410 invoked by uid 22791); 27 Jul 2012 17:07:15 -0000 X-SWARE-Spam-Status: No, hits=-6.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 27 Jul 2012 17:07:03 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q6RH6xVV027927 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 27 Jul 2012 13:06:59 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q6RH6wkY006729 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 27 Jul 2012 13:06:58 -0400 From: Tom Tromey To: Yao Qi Cc: Subject: Re: [RCF 0/6 V2] MI notification of command option change References: <1343402543-665-1-git-send-email-yao@codesourcery.com> Date: Fri, 27 Jul 2012 17:07:00 -0000 In-Reply-To: <1343402543-665-1-git-send-email-yao@codesourcery.com> (Yao Qi's message of "Fri, 27 Jul 2012 23:22:17 +0800") Message-ID: <876299cevh.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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 X-SW-Source: 2012-07/txt/msg00699.txt.bz2 >>>>> "Yao" == Yao Qi writes: Yao> 2. Don't emit option change of all gdb commands. We have to Yao> set 'reporting' commands via function 'set_cmd_notify', otherwise Yao> commands are still 'no-reporting'. I believe that frontends will Yao> request more and more options changes, but changes of some gdb Yao> options are useless to frontends. It is noisy to send all option Yao> changes. Yesterday's discussions convinced me that the best route is to report all changes. If it is really necessary to throttle changes, then I think there should be a new MI command so that the MI client can specify which ones it does or does not want to see. Tom