From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6866 invoked by alias); 23 Nov 2012 01:35:33 -0000 Received: (qmail 6712 invoked by uid 22791); 23 Nov 2012 01:35:32 -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, 23 Nov 2012 01:35:11 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1TbiAf-0007PY-R4 from Yao_Qi@mentor.com ; Thu, 22 Nov 2012 17:35:09 -0800 Received: from SVR-ORW-FEM-02.mgc.mentorg.com ([147.34.96.206]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 22 Nov 2012 17:35:09 -0800 Received: from qiyao.dyndns.org (147.34.91.1) by svr-orw-fem-02.mgc.mentorg.com (147.34.96.168) with Microsoft SMTP Server id 14.1.289.1; Thu, 22 Nov 2012 17:35:08 -0800 Message-ID: <50AED2C7.1040708@codesourcery.com> Date: Fri, 23 Nov 2012 01:35: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: "gdb@sourceware.org" Subject: Re: gdb in non-stop/sync mode connects to gdbserver References: <50AE4E3D.8000701@codesourcery.com> <50AE6BFF.5050008@redhat.com> In-Reply-To: <50AE6BFF.5050008@redhat.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-11/txt/msg00069.txt.bz2 On 11/23/2012 02:16 AM, Pedro Alves wrote: > "non-stop and sync mode" is really not supported. non-stop is defined to > work only with async on. There are many such assumptions in the code. That the > test works in sync mode on native is just an accident. I had a vague impression that "non-stop" works on top of async mode before. However, I was misled by the code that 'target_can_async_p' is checked on 'non-stop' path, and accordingly think "non-stop may work on sync mode". Anyway, thanks for confirming this. -- Yao (齐尧)