From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from progateway7-pub.mail.pro1.eigbox.com (gproxy5-pub.mail.unifiedlayer.com [67.222.38.55]) by sourceware.org (Postfix) with ESMTPS id EF4603858C74 for ; Wed, 9 Mar 2022 19:49:17 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org EF4603858C74 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 cmgw14.mail.unifiedlayer.com (unknown [10.0.90.129]) by progateway7.mail.pro1.eigbox.com (Postfix) with ESMTP id 5693C1004720A for ; Wed, 9 Mar 2022 19:49:17 +0000 (UTC) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with ESMTP id S2JAnAAKa2s5dS2JBnrJAL; Wed, 09 Mar 2022 19:49:17 +0000 X-Authority-Reason: nr=8 X-Authority-Analysis: v=2.4 cv=BOh2EHcG c=1 sm=1 tr=0 ts=622904bd 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=Ti1SOEOaIJ1piJE0htQA:9 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=L1zQ2Wer4QdBmK1ci7KK/8zew/CEv2/nKj/+1DkUQuk=; b=ofsP8SW+EBdFfp3TFrcP0l/0gg whXJXWO4EAwCXPbQXb69W8pFFg+DgfR+eX7QuKefsPRAx7kLUp8TNePwKZ8ESVvezmHGsoj330oeF c4wnTH9BQUoORaZFLQjYcy6zo; Received: from 75-166-141-253.hlrn.qwest.net ([75.166.141.253]:40574 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 1nS2JA-002k1E-HK; Wed, 09 Mar 2022 12:49:16 -0700 From: Tom Tromey To: Adrian Oltean Cc: Tom Tromey , Adrian Oltean via Gdb Subject: Re: Semihosting in GDB 11.1 | Proposed patch for interrupting in sync mode References: X-Attribution: Tom Date: Wed, 09 Mar 2022 12:49:15 -0700 In-Reply-To: (Adrian Oltean's message of "Wed, 9 Mar 2022 07:25:36 +0000") Message-ID: <87k0d2gb44.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: 1nS2JA-002k1E-HK X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: 75-166-141-253.hlrn.qwest.net (prentzel) [75.166.141.253]:40574 X-Source-Auth: tom+tromey.com X-Email-Count: 2 X-Source-Cap: ZWx5bnJvYmk7ZWx5bnJvYmk7Ym94NTM3OS5ibHVlaG9zdC5jb20= X-Local-Domain: yes X-Spam-Status: No, score=-3024.4 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: Wed, 09 Mar 2022 19:49:19 -0000 Adrian> Unfortunately, I could not find ways to adapt all the other components I have around GDB to Adrian> work with target-async mode enabled. It is what it is... I'm a little lost about this, because my mental model is that target async shouldn't really change anything. I think it is just an implementation detail about where gdb waits for events -- is it in wait() or in select()? So, it would be interesting to learn what the differences are. Perhaps this can be patched up. Adrian> Regarding the 'H' packet, I had a second look in the RSP specs Adrian> where it's stated that '0' indicates an arbitrary Adrian> process/thread. So, as you mentioned, I changed the GDB server Adrian> code to simply ensure there's a valid thread stopped marked as Adrian> 'current'. The original implementation incorrectly assimilated Adrian> '0' with 'first thread' (always). I'm a little surprised this matters as well, but anyway I think it's fine to submit a patch like this. Maybe others have some idea of what's going on. Tom