From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7643 invoked by alias); 18 Sep 2012 14:39:10 -0000 Received: (qmail 7633 invoked by uid 22791); 18 Sep 2012 14:39:09 -0000 X-SWARE-Spam-Status: No, hits=-4.0 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 imr3.ericy.com (HELO imr3.ericy.com) (198.24.6.13) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 18 Sep 2012 14:38:51 +0000 Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q8IEcnBx007610 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 18 Sep 2012 09:38:49 -0500 Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.2.164]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Tue, 18 Sep 2012 10:38:48 -0400 From: Marc Khouzam To: "'Yao Qi'" CC: "'gdb-patches@sourceware.org'" Date: Tue, 18 Sep 2012 14:39:00 -0000 Subject: RE: [RFC 0/2, gdbserver] Set linux target in async mode in default Message-ID: References: <1347961672-18495-1-git-send-email-yao@codesourcery.com> <5058868F.7070703@codesourcery.com> In-Reply-To: <5058868F.7070703@codesourcery.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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-09/txt/msg00361.txt.bz2 > -----Original Message----- > From: Yao Qi [mailto:yao@codesourcery.com]=20 > Sent: Tuesday, September 18, 2012 10:35 AM > To: Marc Khouzam > Cc: 'gdb-patches@sourceware.org' > Subject: Re: [RFC 0/2, gdbserver] Set linux target in async=20 > mode in default >=20 > On 09/18/2012 10:12 PM, Marc Khouzam wrote: > > To clarify, after this patch we can still use "-gdb-set=20 > target-async off" > > to turn off async mode right? > > >=20 > This patch doesn't change the behaviour from the GDB's and Eclipse's=20 > perspective. We can still set target-async on or off in GDB=20 > side as needed. >=20 > IIUC, the term "async mode" in GDBserver is different from its=20 > counterpart in GDB. In GDBserver, "async mode" means an "async event=20 > loop" which is used for non-stop and notification. If we look at RSP, > there is no command to turn "async mode" on or off directly=20 > in GDBserver=20 > (QNonStop can start async mode on linux target), the state of "async=20 > mode" of GDBserver is unknown to GDB, and vice versa. Sorry, I missed that this was for gdbserver only. >=20 > In current GDBserver/linux, we have only two modes, 'non-stop with=20 > async-event-loop' and 'all-stop without async-event-loop'.=20=20 > This patch=20 > only changes the latter to 'all-stop with async-event-loop', so that=20 > async notification can work on top it. At the same time, GDB still=20 > works in both "target-async on" and "target-async off" with=20 > this patched=20 > GDbserver. >=20 > > Eclipse currently uses non-async mode for all-stop and some code > > is based on that assumption (e.g., interrupting the target) > > so we need to keep non-async available. >=20 > Forgot to mention in my mail that I run testsuite with=20 > {native-gdbserver, native-extended-gdbserver} x {async, sync} (in GDB=20 > side), and no regression. >=20 > --=20 > Yao >=20