Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Keith Seitz via Gdb <gdb@sourceware.org>
To: Guinevere Larsen <blarsen@redhat.com>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Wondering if record save should be deprecated
Date: Thu, 11 Jul 2024 09:52:41 -0700	[thread overview]
Message-ID: <0305acfe-2eed-4c2c-a28c-cf4542129131@redhat.com> (raw)
In-Reply-To: <3efbc686-a7ec-4699-85ba-b96ea4ec2bad@redhat.com>

On 7/10/24 12:58 PM, Guinevere Larsen via Gdb wrote:
> Hi everyone!

Warning: I am not a record/replay user.

> Does it make sense for us to continue supporting this feature that was 
> nigh unusable for 5 releases without anyone noticing? Does anyone 
> reading this makes use of this feature and managed to somehow avoid that 
> crash?

 From the User Manual:

record save filename

     Save the execution log to a file filename. Default filename is 
gdb_record.process_id, where process_id is the process ID of the inferior.

     This command may not be available for all recording methods.


This certainly sounds like a useful feature to have/keep/make work.
I can envision some use cases where this would really be useful.

That said, I would not be quick to confuse utility with awareness.
GDB has so many features nowadays that even as a developer/packager
for it, I feel I barely use more than 25-30% of GDB's available
features.

My vote is to fix it, test it, and keep it.

Keith


  reply	other threads:[~2024-07-11 16:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-10 19:58 Guinevere Larsen via Gdb
2024-07-11 16:52 ` Keith Seitz via Gdb [this message]
2024-07-16 12:24 ` Luis Machado via Gdb
2024-07-16 13:27   ` Guinevere Larsen via Gdb

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=0305acfe-2eed-4c2c-a28c-cf4542129131@redhat.com \
    --to=gdb@sourceware.org \
    --cc=blarsen@redhat.com \
    --cc=keiths@redhat.com \
    /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