Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb-patches@sourceware.org, thiago.bauermann@linaro.org
Subject: Re: [PATCH v2 6/6] gdb/record: Define new version of the record-save section
Date: Thu, 23 Apr 2026 18:45:38 +0300	[thread overview]
Message-ID: <867bpxbrz1.fsf@gnu.org> (raw)
In-Reply-To: <20260423152604.171356-7-guinevere@redhat.com> (message from Guinevere Larsen on Thu, 23 Apr 2026 12:26:04 -0300)

> From: Guinevere Larsen <guinevere@redhat.com>
> Cc: Guinevere Larsen <guinevere@redhat.com>,
>  Thiago Jung Bauermann <thiago.bauermann@linaro.org>
> Date: Thu, 23 Apr 2026 12:26:04 -0300
> 
> With the changes to the internal representation of the history, we can
> no longer support the previous record save format. This commit makes it
> official, documenting the new format and changing the magic number.
> 
> Reviewed-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
> ---
>  gdb/NEWS          |  4 ++++
>  gdb/record-full.c | 35 +++++++++++++++++++++++++++++++----
>  2 files changed, 35 insertions(+), 4 deletions(-)

Thanks, the NEWS part is okay.

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

      reply	other threads:[~2026-04-23 15:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23 15:25 [PATCH v2 0/6] refactor the internals of record-full Guinevere Larsen
2026-04-23 15:25 ` [PATCH v2 1/6] gdb/record: Refactor record history Guinevere Larsen
2026-04-28  3:28   ` Thiago Jung Bauermann
2026-04-28 19:54     ` Guinevere Larsen
2026-05-06 21:16   ` Schimpe, Christina
2026-05-07 17:38     ` Guinevere Larsen
2026-05-11 15:23       ` Schimpe, Christina
2026-05-12 18:50         ` Guinevere Larsen
2026-05-13  7:54           ` Schimpe, Christina
2026-05-14 15:20             ` Guinevere Larsen
2026-04-23 15:26 ` [PATCH v2 2/6] gdb/record: remove record_full_insn_num Guinevere Larsen
2026-04-23 15:26 ` [PATCH v2 3/6] gdb/record: c++ify internal structures of record-full.c Guinevere Larsen
2026-04-28  3:29   ` Thiago Jung Bauermann
2026-04-23 15:26 ` [PATCH v2 4/6] gdb/record: make record_full_history more c++-like Guinevere Larsen
2026-04-28  3:29   ` Thiago Jung Bauermann
2026-04-23 15:26 ` [PATCH v2 5/6] gdb/record: extract the PC to record_full_instruction Guinevere Larsen
2026-04-28  3:30   ` Thiago Jung Bauermann
2026-04-23 15:26 ` [PATCH v2 6/6] gdb/record: Define new version of the record-save section Guinevere Larsen
2026-04-23 15:45   ` Eli Zaretskii [this message]

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=867bpxbrz1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=guinevere@redhat.com \
    --cc=thiago.bauermann@linaro.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