From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=9dVc=EU=vrany.io=jan@sourceware.org>
Received: from mail-4018.proton.ch (mail-4018.proton.ch [185.70.40.18])
	by sourceware.org (Postfix) with ESMTPS id EC1B93858D32
	for <gdb@sourceware.org>; Mon,  4 Sep 2023 21:41:25 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org EC1B93858D32
Authentication-Results: sourceware.org; dmarc=pass (p=quarantine dis=none) header.from=vrany.io
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=vrany.io
Date: Mon, 04 Sep 2023 21:41:18 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vrany.io;
	s=protonmail; t=1693863682; x=1694122882;
	bh=qCCp5/qjrk+mKqz6tO583DhR1Hl++FU7xcVXnACobLA=;
	h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date:
	 Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector;
	b=lZ3bzgk/a3jzmsg5XgFzMGSbFJtGfWYh81cKi+5meR9SiZEVTRZDViMmGqZxEt9Ck
	 NbRbxQttEJaUQ5LLNRSWC88gSsucMfWFUVaEYuzt1LsjtlOtHRw16BWPvU4XdVxg/V
	 uR2pshckzTPXJGXDZPD8bApWYP4Jm32FlXaDNXQTFCNwiIuA9zTw7mDivwZ37Zj+HO
	 77uqlg/h89yjLavcDsCCLzgpL8n0BeR/coxeYe5T6rElJ0eOaQU+zFJUMSCg+CxpZp
	 0k1DZ1uroFKw3Gcgyq3J7NUJx8o+1EXlcgQJgrB05JR5dqRQ5dVo8SPGj5t9sqp3M7
	 c3k1bt7NBEQlA==
To: GDB mailing list <gdb@sourceware.org>
From: Jan Vrany <jan@vrany.io>
Subject: MI and modifying register value
Message-ID: <459b4b9d5f83a6b03b66486a45f5c4e4daa0b5e7.camel@vrany.io>
Feedback-ID: 40767693:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org
List-Id: <gdb.sourceware.org>

Hi,=20

while investigating MI client issue when setting a register value
from debugger I realized two things:=20

1) There's an MI command to set register value: -data-write-register-values
   This command is not documented and looking at the code, seems to be some=
what
   half-implemented - does not use <format> parameter its comment mentions =
and
   only works for frame 0 (but using --frame 1 does not result in an error,
   it just silently changes value in frame 0).=20

   Is this command some leftover that should not be used (but kept for some
   old clients)? Or is it something to fix?=20

2) Another way to change register value is CLI command `set r4 =3D 0x4`. Th=
ere's
   no mechanism the MI client gets notified about the change - there's no =
=3Dregister-changed
   async event.=C2=A0

   Is this by purpose? I'd expect some kind of notification, just like ther=
e's =3Dmemory-changed
   event. Also, in Python API, there's memory_ckanged event which get trigg=
ered when
   using `set` to modify register.=20

Best, Jan

  =20