From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26936 invoked by alias); 30 Jun 2016 11:46:48 -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 26918 invoked by uid 89); 30 Jun 2016 11:46:43 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy= X-HELO: usplmg21.ericsson.net Received: from usplmg21.ericsson.net (HELO usplmg21.ericsson.net) (198.24.6.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Thu, 30 Jun 2016 11:46:41 +0000 Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usplmg21.ericsson.net (Symantec Mail Security) with SMTP id 1F.81.03614.F5605775; Thu, 30 Jun 2016 13:45:35 +0200 (CEST) Received: from elxa4wqvvz1 (147.117.188.8) by smtps-am.internal.ericsson.com (147.117.188.96) with Microsoft SMTP Server (TLS) id 14.3.294.0; Thu, 30 Jun 2016 07:46:38 -0400 References: <1465476975-25062-1-git-send-email-antoine.tremblay@ericsson.com> <0d896cd9-f857-db41-fdb1-2ebde0eeeb01@redhat.com> <259cec78-8993-e31a-2d8e-d16d96a34a7a@redhat.com> User-agent: mu4e 0.9.17; emacs 24.4.1 From: Antoine Tremblay To: Pedro Alves CC: Antoine Tremblay , Subject: Re: [PATCH v2 00/17] Fast tracepoint support for ARMv7 In-Reply-To: <259cec78-8993-e31a-2d8e-d16d96a34a7a@redhat.com> Date: Thu, 30 Jun 2016 11:46:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2016-06/txt/msg00533.txt.bz2 Pedro Alves writes: > On 06/29/2016 08:15 PM, Antoine Tremblay wrote: >> >> Pedro Alves writes: > > >> OK, I guess I have to find a way to interrupt it, in my case using a >> circular buffer, trying c& and interrupt as no effect or C-c with >> continue... > > Sounds like a gdbserver bug. :-/ You should always be able to > interrupt. Seems like what you'd get if the signal ends up in the > pending queue, but is then never reported, for whatever reason. > If this is non-stop, could also be related to stopping > with SIGSTOP, which requires special treatment. Try > with "kill -SIGINT" in the terminal too. > OK. I tried all-stop and non-stop now and in all-stop I can't interrupt even with a kill -SIGINT from the term. However in non-stop it works fine, with interrupt or C-c. Guess I'll have to fix this first... Thanks, Antoine