Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: 郭胜元 <guoshengyuan1@xiaomi.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [External Mail]Re: [PATCH] [gdb/python]: add the orginal_value field in RegisterChangedEvent
Date: Mon, 29 Sep 2025 04:23:43 +0000	[thread overview]
Message-ID: <c912d8a4-3ce2-45fa-8970-6500cfe854bf@xiaomi.com> (raw)
In-Reply-To: <86qzvq6aor.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2108 bytes --]

在 2025/9/28 20:09, Eli Zaretskii 写道:

From: guoshengyuan1 <guoshengyuan1@xiaomi.com><mailto:guoshengyuan1@xiaomi.com>
CC: guoshengyuan1 <guoshengyuan1@xiaomi.com><mailto:guoshengyuan1@xiaomi.com>
Date: Sun, 28 Sep 2025 19:18:08 +0800

When the register_changed event is triggered, the user should be told
what the previous value was so they can make a decision, rather
than just being told what the modified value is.

Signed-off-by: guoshengyuan1 <guoshengyuan1@xiaomi.com><mailto:guoshengyuan1@xiaomi.com>
---
 gdb/doc/python.texi                   |  3 +++
 gdb/observable.h                      |  4 +++-
 gdb/python/py-event.h                 |  2 +-
 gdb/python/py-inferior.c              |  6 ++++--
 gdb/python/py-infevents.c             | 19 ++++++++++++++++---
 gdb/testsuite/gdb.python/py-events.py |  1 +
 gdb/tui/tui-hooks.c                   |  4 +++-
 gdb/valops.c                          |  4 +++-
 8 files changed, 34 insertions(+), 9 deletions(-)



Thanks, the python.texi part is okay.

Should this be called out in NEWS as well?

Reviewed-By: Eli Zaretskii <eliz@gnu.org><mailto:eliz@gnu.org>


What you said makes sense. I think this API change should be mentioned in the NEWS. Do I need to write the NEWS?

#/******本邮件及其附件含有小米公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件! This e-mail and its attachments contain confidential information from XIAOMI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!******/#

[-- Attachment #2: Type: text/html, Size: 2872 bytes --]

  reply	other threads:[~2025-09-29  4:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-28 11:18 guoshengyuan1
2025-09-28 12:09 ` Eli Zaretskii
2025-09-29  4:23   ` 郭胜元 [this message]
2025-09-29 11:09     ` [External Mail]Re: " Eli Zaretskii
2025-09-28 15:59 ` Andrew Burgess
2025-09-29  7:47   ` [External Mail]Re: " 郭胜元
2025-10-06 16:01     ` Andrew Burgess

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c912d8a4-3ce2-45fa-8970-6500cfe854bf@xiaomi.com \
    --to=guoshengyuan1@xiaomi.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox