From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21980 invoked by alias); 22 Nov 2012 18:16:38 -0000 Received: (qmail 21970 invoked by uid 22791); 22 Nov 2012 18:16:37 -0000 X-SWARE-Spam-Status: No, hits=-7.9 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS 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; Thu, 22 Nov 2012 18:16:34 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qAMIGXab020244 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 22 Nov 2012 13:16:33 -0500 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id qAMIGVdV008887; Thu, 22 Nov 2012 13:16:32 -0500 Message-ID: <50AE6BFF.5050008@redhat.com> Date: Thu, 22 Nov 2012 18:16:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Yao Qi CC: "gdb@sourceware.org" Subject: Re: gdb in non-stop/sync mode connects to gdbserver References: <50AE4E3D.8000701@codesourcery.com> In-Reply-To: <50AE4E3D.8000701@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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/msg00066.txt.bz2 On 11/22/2012 04:09 PM, Yao Qi wrote: > Hello, > When running moribund-step.exp with boardfile 'unix', we'll get two passes, > > PASS: gdb.base/moribund-step.exp: set non-stop on > PASS: gdb.base/moribund-step.exp: step > > However, when running it with boardilfe native-gdbserver, we'll get only one pass, > > PASS: gdb.base/moribund-step.exp: set non-stop on > > in fact, gdb hang there when connecting to gdbserver. Supposing gdb is in non-stop and sync mode, here is callgraph of functions related to 'connecting to remote gdbserver'. "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. -- Pedro Alves