From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id RG9kIPdWi2WibisAWB0awg (envelope-from ) for ; Tue, 26 Dec 2023 17:43:03 -0500 Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=M0BVFF5C; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 7613A1E0C3; Tue, 26 Dec 2023 17:43:03 -0500 (EST) Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 2B0A11E0AC for ; Tue, 26 Dec 2023 17:43:01 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 5AA693858285 for ; Tue, 26 Dec 2023 22:43:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5AA693858285 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1703630580; bh=L04s2jqWKKPht2OKI/vKHhSy3nQYdtx1CuN9Bhay14U=; h=Date:To:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=M0BVFF5CG4ar/5Z9BOAMxn6RfwEThp8Zr5StU26vf5DFg3aJ5kMj4VMFVf16h71ON jljcXH2bikEdReFafg+wjicFUuAvH7iEudMfUOz5rDitD7RSEdkbWMjXzZhRrvpyEq jFECUkMk2L3OpLd6pf6yENlP5aNB4y28jGhg8A08= Received: from mail.zytor.com (unknown [IPv6:2607:7c80:54:3::138]) by sourceware.org (Postfix) with ESMTPS id C60943858430 for ; Tue, 26 Dec 2023 22:42:18 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org C60943858430 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org C60943858430 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1703630541; cv=none; b=BvxEg2gM/Db66z9L4qocJdnug8+Kif7qBsY/wLDUmXlvUNot/bY/PxmPdQ04yU5CDzzL9TSPLs4XrdSGfP4oBsHB/Wf/xV+e20f2av2j6RKU+YRVjpUPbmZ9EVc/07+fGN3XLXBZCrx7048T6ROWFDzTi3dwmbS0CobVBmkm6uc= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1703630541; c=relaxed/simple; bh=dIwrm3Z+VJRUwPBGPccARcM4hUCYa2HgKRWZ+6xcKBo=; h=DKIM-Signature:Message-ID:Date:MIME-Version:To:From:Subject; b=NPvGGYXdNFEnPJz/tNJ1qvnrnosMTofbDADiUHF2DLD3ka2TV2hve48j+iLaV1eNJcQZCOrVdGxjxBzqWDF0aLEwymeYpzFku1Z2cHx1PX9v7lTSAinrLloZoZesW6AwfY9GErWje+WOxN/DDW3+twmLTDXtk/RqB0RtOufBvWo= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from [IPV6:2601:646:8002:4641:eb14:ad94:2806:1c1a] ([IPv6:2601:646:8002:4641:eb14:ad94:2806:1c1a]) (authenticated bits=0) by mail.zytor.com (8.17.2/8.17.1) with ESMTPSA id 3BQMgDiG370614 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Tue, 26 Dec 2023 14:42:14 -0800 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.zytor.com 3BQMgDiG370614 Message-ID: Date: Tue, 26 Dec 2023 14:42:08 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: gdb@sourceware.org Content-Language: en-US Subject: Questions on XML register descriptions Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "H. Peter Anvin via Gdb" Reply-To: "H. Peter Anvin" Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" Hi, I have been looking at the XML register descriptions, and I have a couple of questions, as I'm trying to add gdb remote support to an emulator, which involves additional system-level registers as well as memory spaces. 1. Some registers can't be written to, and some registers may affect other registers. What, if anything, is the best way to handle that? 2. How do the G/g commands interact with the XML target descriptions? Do they apply specifically to group="general", or are there other rules? 3. Is there any concept at all of different address spaces in gdb? Alternatively, is there any way to tell gdb that it should communicate addresses wider than the pointer type of the base architecture (which would allow a Python helper script to define a convenience API.) 4. There doesn't seem to be a way to trigger a Python function when a connection is *established*, which is as far as I understand the point at which the XML register description is downloaded from the remote, and definitely the first point at which register values can be examined. Am I missing something obvious? 5. I presume the byte codes use for the Z commands are the same as the agent bytecode in Appendix F, even though the latter specifically seems to be referring to tracepoints? Many thanks, -hpa