From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 48546 invoked by alias); 23 Dec 2019 16:32:32 -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 48538 invoked by uid 89); 23 Dec 2019 16:32:32 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-4.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=H*f:sk:i2L-gcY, H*i:sk:i2L-gcY, H*i:CAHrp7QDosAYw2k, H*f:CAHrp7QDosAYw2k X-HELO: pb-smtp21.pobox.com Received: from pb-smtp21.pobox.com (HELO pb-smtp21.pobox.com) (173.228.157.53) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 23 Dec 2019 16:32:30 +0000 Received: from pb-smtp21.pobox.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 7279EB736F for ; Mon, 23 Dec 2019 11:32:28 -0500 (EST) (envelope-from jonah@kichwacoders.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type; s=sasl; bh=4OdppJMCtc473gzWDAZ3Nj6jMZ4=; b=X6I65h nMEVThSrLBxN6YEYfPDkAPmaB/d92CnYN9KxASoql2oCyhH8WzWWnb2HbnC0LKdZ 1n++G5aDz3xeHLUQ4y5MZeTMntbUQzYZ5xyLe2f1k0u5uN6gSc3aSbWoUBy1HsNw 3uXv0FXztsqjXGWg76mQyFdHyWSzC0f4aQCUk= Received: from pb-smtp21.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 6AE78B736E for ; Mon, 23 Dec 2019 11:32:28 -0500 (EST) (envelope-from jonah@kichwacoders.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=kichwacoders.com; h=mime-version:references:in-reply-to:from:date:message-id:subject:to:cc:content-type; s=mesmtp; bh=+6dOHNHK37dxIN/HE7XHvcCJzYzuXZSbSXkilGWS1IA=; b=X35FaB4AwEDciHYP6C5PV+DAFD5Kw2PIn+nBnrFxm1IC5KoASGI9mahGytHl4RaiHSeB/WnSVttdUfEAHiTyqvzWEBXmWkdGyVa2WcqmQ0mIFpdL5Z9FhPcdUtpN0IftK4ebFu/jUBcH1J2kyyGAoaVXul6OJ750Odk1lHNFEnc= Received: from mail-qk1-f181.google.com (unknown [209.85.222.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp21.pobox.com (Postfix) with ESMTPSA id 0B639B736D for ; Mon, 23 Dec 2019 11:32:25 -0500 (EST) (envelope-from jonah@kichwacoders.com) Received: by mail-qk1-f181.google.com with SMTP id t129so13928790qke.10 for ; Mon, 23 Dec 2019 08:32:25 -0800 (PST) MIME-Version: 1.0 References: <31d23a62-eef1-63d4-f992-a0b553b141b9@redhat.com> In-Reply-To: From: Jonah Graham Date: Mon, 23 Dec 2019 16:32:00 -0000 Message-ID: Subject: Re: GDB doesn't interrupt target To: Tudor Popescu Cc: Pedro Alves , GDB Development Content-Type: text/plain; charset="UTF-8" X-Pobox-Relay-ID: CD2F3A48-25A1-11EA-B5F9-8D86F504CC47-18936988!pb-smtp21.pobox.com X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00051.txt.bz2 On Mon, 23 Dec 2019 at 09:37, Tudor Popescu wrote: > > Hello, > > I have tracked the problem to a link: > Wiki.eclipse.org/CDT/FullGDBConsole. > Junit test failures #2 and things to work on #1 are the exact descriptions of my problem. The page hasn't been updated since 2016. Thanks Tudor for pointing out this document on the Wiki - it was a status report on the development of the new feature and does not represent the released state of CDT. I have marked the page as obsolete. > Can you tell me how were these issues addressed? The key part - async comms - cam as part of CDT 9.2 when the new-ui was rolled out. See the New and Noteworthy: https://wiki.eclipse.org/CDT/User/NewIn92#Running_All-stop_mode_Asynchronously Please raise a bug (https://bugs.eclipse.org/bugs/enter_bug.cgi?product=CDT) in CDT with the details and I can look at it further. In addition to the version of those bundles, I need what launch configuration you are using. You can either share your .launch file, or if that is not possible tell me what is selected in Debug Configurations dialog on the left (launch config type) and if present which launcher (this area, next to revert/apply buttons may be blank). See https://i.imgur.com/wIkAb0U.png And it would be most useful to include the MI trace to see what is going wrong. If it off by default, but you can turn it on in Preferences -> C/C++ -> Debug -> GDB and check "Show the GDB traces [...]". Once enabled the Console view will display the MI trace. I hope we can get to the bottom of this. Jonah