From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 47748 invoked by alias); 22 Jan 2016 17:14:16 -0000 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 Received: (qmail 47736 invoked by uid 89); 22 Jan 2016 17:14:15 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=determined, Hx-languages-length:692, resumes, Hx-spam-relays-external:209.85.192.170 X-HELO: mail-pf0-f170.google.com Received: from mail-pf0-f170.google.com (HELO mail-pf0-f170.google.com) (209.85.192.170) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 22 Jan 2016 17:14:14 +0000 Received: by mail-pf0-f170.google.com with SMTP id e65so45344403pfe.0 for ; Fri, 22 Jan 2016 09:14:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-type :content-transfer-encoding; bh=T1vhyvo766e//jUVMiELu8jlpVP7YtQBiSMXCfs+CQk=; b=i06tokIiejoWbZ/x/a5Z/ccvL20/IPTBcrtaTfVu17AaGtPkXg9uI4Uoz05smMDMrj DGOxucPmGJo8RWD7PWfXgtpSQG4NuDKbIT5iofmGZs/W4AVd2UL/MQ3m8e9NrSCbxSvC IaB1KqgyG9gamKDBldXwTWScptGQaFYTxQdRt8UIGSbtOfNXhcXsul/mZOoS4WIbUVaN lu3BwvIDOkyogD72J6lSlUCoNQ8Ip1AKPkVxwhzGO2TfOdJLrUGd/rFDru0y82yetrfw S1bt2b1VvvyyGyB88PEPCWOdaIqc9zdmyPW8PIU4tdIsw7reYzDC+ioHZfjnoHn3iVUi vmGw== X-Gm-Message-State: AG10YOTv8e2eE05RdjTOjcAe1bY7TaA96x78YrRz4igCvrUE/XQvaYtbRjPEFo5HWtBuhA== X-Received: by 10.98.68.193 with SMTP id m62mr5981982pfi.153.1453482852659; Fri, 22 Jan 2016 09:14:12 -0800 (PST) Received: from E107787-LIN (gcc1-power7.osuosl.org. [140.211.15.137]) by smtp.gmail.com with ESMTPSA id fl9sm10977741pab.33.2016.01.22.09.14.10 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Fri, 22 Jan 2016 09:14:11 -0800 (PST) From: Yao Qi To: Pedro Alves Cc: Yao Qi , gdb-patches@sourceware.org Subject: Re: [PATCH] Fix fail in gdb.base/interrupt-noterm.exp References: <1453480183-5131-1-git-send-email-yao.qi@linaro.org> <56A25D13.2080608@redhat.com> Date: Fri, 22 Jan 2016 17:14:00 -0000 In-Reply-To: <56A25D13.2080608@redhat.com> (Pedro Alves's message of "Fri, 22 Jan 2016 16:47:15 +0000") Message-ID: <86twm5r0yp.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2016-01/txt/msg00576.txt.bz2 Pedro Alves writes: > Can you expand the rationale some more? > > E.g., why is this not a gdbserver bug? Instintively I'd say it is. The interaction between GDB and GDBserver is like this, 1. GDB sends vCont;c and doesn't wait for the stop reply because "continue &" is background command, 2. GDBserver receives vCont;c, enables the async i/o (by enable_async_io) and resumes the inferior. 3. GDB sends interrupt packet, #1 happens before #2 and #3, but the order of #2 and #3 is not determined. If #2 happens before #3, it is fine, otherwise, the GDBserver doesn't know the interrupt from GDB. --=20 Yao (=E9=BD=90=E5=B0=A7)