public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "epasveer at att dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/30356] gdb/mi equivalent for "checkpoint"
Date: Mon, 08 May 2023 20:18:12 +0000	[thread overview]
Message-ID: <bug-30356-4717-OIGtXtJES9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30356-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Ernie Pasveer <epasveer at att dot net> ---
Hi Tom,

Can you elaborate more the the "python hack" approach.  I can at least
investigate that. I suspect it would mean the output from the python code would
follow the form of gdb/mi stream channels. ie:

    -checkpoint-create

    -checkpoint-list
    ^done,CheckpointTable={nr_rows="1",nr_cols="4", ...

    -checkpoint-restore N

The python code would accept these "new" commands and somehow morph them into
the native gdb commands.

https://sourceware.org/gdb/current/onlinedocs/gdb.html/Checkpoint_002fRestart.html#Checkpoint_002fRestart


Perhaps you can point me to the resources to make custom commands in python.

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

  parent reply	other threads:[~2023-05-08 20:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 19:28 [Bug mi/30356] New: " epasveer at att dot net
2023-04-22  0:25 ` [Bug mi/30356] " tromey at sourceware dot org
2023-05-08 20:18 ` epasveer at att dot net [this message]
2023-05-09 18:12 ` tromey at sourceware dot org
2025-09-22 16:49 ` epasveer at att dot net

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-30356-4717-OIGtXtJES9@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).