From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gproxy3-pub.mail.unifiedlayer.com (gproxy3-pub.mail.unifiedlayer.com [69.89.30.42]) by sourceware.org (Postfix) with ESMTPS id 45EA33858C83 for ; Tue, 8 Mar 2022 22:10:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 45EA33858C83 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=tromey.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=tromey.com Received: from cmgw13.mail.unifiedlayer.com (unknown [10.0.90.128]) by progateway5.mail.pro1.eigbox.com (Postfix) with ESMTP id 91E2F10047F3A for ; Tue, 8 Mar 2022 22:10:15 +0000 (UTC) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with ESMTP id Ri23nsMZsY8ycRi23nUEM2; Tue, 08 Mar 2022 22:10:15 +0000 X-Authority-Reason: nr=8 X-Authority-Analysis: v=2.4 cv=Ue6U9IeN c=1 sm=1 tr=0 ts=6227d447 a=ApxJNpeYhEAb1aAlGBBbmA==:117 a=ApxJNpeYhEAb1aAlGBBbmA==:17 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=o8Y5sQTvuykA:10:nop_rcvd_month_year a=Qbun_eYptAEA:10:endurance_base64_authed_username_1 a=CCpqsmhAAAAA:8 a=wiLCuWvnh_jX3AgUFtMA:9 a=ul9cdbp4aOFLsgKbc677:22 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:References :Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=FV4tMSe1E6w1mYWBWIKpBI6/2qLBoQZ5A0CiSFpMO5Y=; b=g3gez7Z80S+my7K3PU1DO2KccG 9p1v0SinS5nYpK9ommMQa9tmzJJUwwUxQk9HHUi03YYrOWMZRdrKKaG5AUhxjlJubMsruKqIx4MdJ 9xq7tLVKNJGRR8M2k0Kr26iWF; Received: from 75-166-141-253.hlrn.qwest.net ([75.166.141.253]:41870 helo=prentzel) by box5379.bluehost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nRi22-0026YQ-Ng; Tue, 08 Mar 2022 15:10:14 -0700 From: Tom Tromey To: Adrian Oltean via Gdb Cc: Adrian Oltean Subject: Re: Semihosting in GDB 11.1 | Proposed patch for interrupting in sync mode References: X-Attribution: Tom Date: Tue, 08 Mar 2022 15:10:14 -0700 In-Reply-To: (Adrian Oltean via Gdb's message of "Mon, 7 Mar 2022 19:39:40 +0000") Message-ID: <871qzc2j09.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box5379.bluehost.com X-AntiAbuse: Original Domain - sourceware.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tromey.com X-BWhitelist: no X-Source-IP: 75.166.141.253 X-Source-L: No X-Exim-ID: 1nRi22-0026YQ-Ng X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: 75-166-141-253.hlrn.qwest.net (prentzel) [75.166.141.253]:41870 X-Source-Auth: tom+tromey.com X-Email-Count: 5 X-Source-Cap: ZWx5bnJvYmk7ZWx5bnJvYmk7Ym94NTM3OS5ibHVlaG9zdC5jb20= X-Local-Domain: yes X-Spam-Status: No, score=-3024.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, JMQ_SPF_NEUTRAL, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2022 22:10:17 -0000 >>>>> Adrian Oltean via Gdb writes: > 1. I need to run GDB client in all-stop mode with target-async set to off. > This seems to be a must in order to make some python scripts (containing > gdb.post_event('continue')) interact correctly with Eclipse CDT and with > some automation I have around the python scripts. I think it would be better on the whole to figure out a way to make this work with target-async. In the long run I'd prefer that gdb remove sync target wait entirely -- that the default be target-async everywhere. > but I'd like to know if there's any chance I'll break > any use case with these changes. I don't have the answer to that I'm afraid. > Is the described behavior a known issue > inside GDB? Or do I have to change something in the server to correct the > described behavior? > [remote] Sending packet: $Hg0#df I think this request means to switch to any thread for subsequent non-continue/step requests. So, ignoring it is almost the right thing to do, I think the idea is just to ensure that some stopped thread is selected. Tom