From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 129449 invoked by alias); 19 Dec 2019 14:22:15 -0000 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 Received: (qmail 128623 invoked by uid 89); 19 Dec 2019 14:22:15 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=H*i:sk:CAHrp7Q, H*i:sk:eZM3eT3, H*f:sk:eZM3eT3, H*r:sk:mail-ed X-HELO: us-smtp-1.mimecast.com Received: from us-smtp-delivery-1.mimecast.com (HELO us-smtp-1.mimecast.com) (207.211.31.120) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 19 Dec 2019 14:22:14 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1576765332; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VzvvPpWdMttCeru0dIwDKPNMnGIWYr4cDlRF5dcE94A=; b=iFtTwJVbw6yCXw/xZ9RJmItDVMzpVi42ZIYOYof4MtoCSiP0V5hLlA0mZDBadUaku8TMAN O2jfId9LyfCPSwU0skoLywIfTplCZ7vgE3sS3Jl8uRQEfaY/3b9xaK0TbL0yrCLtE05/Q4 jlZOttFhZJa77uRXl7GBur7nIteC104= Received: from mail-ed1-f69.google.com (mail-ed1-f69.google.com [209.85.208.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-9-afWzNlI7NgW3X4xfAgGMgQ-1; Thu, 19 Dec 2019 09:22:11 -0500 Received: by mail-ed1-f69.google.com with SMTP id c24so638682edy.9 for ; Thu, 19 Dec 2019 06:22:11 -0800 (PST) Return-Path: Received: from ?IPv6:2001:8a0:f913:f700:56ee:75ff:fe8d:232b? ([2001:8a0:f913:f700:56ee:75ff:fe8d:232b]) by smtp.gmail.com with ESMTPSA id p24sm426592eds.17.2019.12.19.06.22.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 19 Dec 2019 06:22:09 -0800 (PST) Subject: Re: GDB doesn't interrupt target To: Tudor Popescu , Jonah Graham References: Cc: GDB Development From: Pedro Alves Message-ID: <31d23a62-eef1-63d4-f992-a0b553b141b9@redhat.com> Date: Thu, 19 Dec 2019 14:22:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-12/txt/msg00037.txt.bz2 On 12/19/19 1:10 PM, Tudor Popescu wrote: > Indeed the "interrupt" works on Debugger Console, as for the Suspend, the console prints a "^CQuit" just as when killing. This suggests that the suspend button is sending a SIGINT to GDB instead of issing an -exec-interrupt command on the MI channel. (MI's -exec-interrupt command is the equivalent of the "interrupt" command on the console.) Thanks, Pedro Alves