From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-35936-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 29821 invoked by alias); 12 Oct 2009 16:15:59 -0000
Received: (qmail 29810 invoked by uid 22791); 12 Oct 2009 16:15:57 -0000
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Received: from smtp-outbound-2.vmware.com (HELO smtp-outbound-2.vmware.com) (65.115.85.73)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 12 Oct 2009 16:15:54 +0000
Received: from mailhost3.vmware.com (mailhost3.vmware.com [10.16.27.45]) 	by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 11A856002 	for <gdb@sourceware.org>; Mon, 12 Oct 2009 09:15:53 -0700 (PDT)
Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) 	by mailhost3.vmware.com (Postfix) with ESMTP id 08153CD99E 	for <gdb@sourceware.org>; Mon, 12 Oct 2009 09:15:53 -0700 (PDT)
Message-ID: <4AD35518.9040606@vmware.com>
Date: Mon, 12 Oct 2009 16:15:00 -0000
From: Michael Snyder <msnyder@vmware.com>
User-Agent: Thunderbird 1.5.0.12 (X11/20080411)
MIME-Version: 1.0
To:  gdb@sourceware.org
Subject: [discuss] Process record -- save and restore to a file
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2009-10/txt/msg00209.txt.bz2

OK, we set this discussion aside over a month ago, until after 7.0.
Time to revive it?  Seemed like the implementation discussion had
more or less stabilized, and we were mostly still discussing the
user interface and docs -- so let's start there.


In the last cycle, we had come down to a UI that looked like this:

Save recording:
   (gdb) record dump <filename>

Restore recording:
   (gdb) core <filename>
   (gdb) record


I would like to remark that the "restore" UI is logical but not
intuitive.  I think it would be helpful to have a single command eg:

   (gdb) record load <filename>

which would do the same as the "core" and "record" commands.

Secondly, I have a suggestion about the command names.
How about
   record save <filename>
   record restore <filename>
instead of
   record dump <filename>
   record load <filename>

What do you guys think?