From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9553 invoked by alias); 12 Oct 2012 12:00:14 -0000 Received: (qmail 9532 invoked by uid 22791); 12 Oct 2012 12:00:11 -0000 X-SWARE-Spam-Status: No, hits=-4.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 12 Oct 2012 12:00:05 +0000 Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1TMduO-0006wy-60 from Yao_Qi@mentor.com ; Fri, 12 Oct 2012 05:00:04 -0700 Received: from SVR-ORW-FEM-04.mgc.mentorg.com ([147.34.97.41]) by SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 12 Oct 2012 05:00:03 -0700 Received: from qiyao.dyndns.org (147.34.91.1) by svr-orw-fem-04.mgc.mentorg.com (147.34.97.41) with Microsoft SMTP Server id 14.1.289.1; Fri, 12 Oct 2012 05:00:02 -0700 Message-ID: <50780646.2030309@codesourcery.com> Date: Fri, 12 Oct 2012 12:00:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120911 Thunderbird/15.0.1 MIME-Version: 1.0 To: Pedro Alves CC: Subject: Re: [RFC 0/2, gdbserver] Set linux target in async mode in default References: <1347961672-18495-1-git-send-email-yao@codesourcery.com> <5061DA66.6020106@redhat.com> In-Reply-To: <5061DA66.6020106@redhat.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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-10/txt/msg00198.txt.bz2 On 09/26/2012 12:23 AM, Pedro Alves wrote: > Please explain better why this is necessary (probably with an example). > What exactly doesn't work if you don't do this change? It sounds as though > this could make gdbserver push notifications down to GDB in all-stop > mode even when it isn't waiting for server replies? Pedro, I think about your question and 'async notification' again, looks we have two options on the timing of sending '%' notifications, 1. in server.c:handle_target_event, in which %Stop is sent, 2. in the place where something interesting happens. For example, if we have a notification trace stop, '%Trace' notification is sent at the end of tracepoint.c:stop_tracing. My original design is to defer *all* notification sent in #1 (handle_target_event), so async mode should be on. Today, I find that notifications except %Stop can be sent in #2, and don't have to put them into #1. If this sounds reasonable to you, this patch set is useless, and I'll revise my 'async notification' patch set in this way. -- Yao