public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "blarsen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug record/31911] New: Execution history should be saved per inferior
Date: Wed, 19 Jun 2024 12:01:22 +0000	[thread overview]
Message-ID: <bug-31911-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=31911

            Bug ID: 31911
           Summary: Execution history should be saved per inferior
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: record
          Assignee: unassigned at sourceware dot org
          Reporter: blarsen at redhat dot com
  Target Milestone: ---

The record subsystem was added to gdb before we could handle multiple inferior.
As such, it was enough to have a global variable that stored things like the
the execution history, the amount of instruction saved and so on (see list of
global variables in gdb/record-full.c).

All this information should be saved on a per-inferior basis. One way to do it
is putting it inside the "class inferior" in gdb/inferior.h; either saving them
directly, or using gdb's registry system (though I'm not sure I like this
second option). Another possibility would be saving the history in the record
target, if information saved in the target is not duplicated across inferiors.

This will improve our ability to record one or many inferiors at once.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

                 reply	other threads:[~2024-06-19 12:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-31911-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).