From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6115 invoked by alias); 4 Jan 2002 22:12:02 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6059 invoked from network); 4 Jan 2002 22:12:00 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 4 Jan 2002 22:12:00 -0000 Received: from redhat.com (reddwarf.cygnus.com [205.180.231.12]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id OAA17971; Fri, 4 Jan 2002 14:11:52 -0800 (PST) Message-ID: <3C36278D.CF860E4D@redhat.com> Date: Fri, 04 Jan 2002 14:12:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2smp i686) X-Accept-Language: en MIME-Version: 1.0 To: "Frank Ch. Eigler" CC: gdb@sources.redhat.com Subject: Re: A copy/save command ... References: <3C341E2D.6050009@cygnus.com> <20020103155801.A12966@nevyn.them.org> <3C352FB8.2010607@cygnus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-01/txt/msg00020.txt.bz2 "Frank Ch. Eigler" wrote: > > cagney wrote: > > > [...] Lets be honest, ``copy'' is a really bad name. For all those > > reasons and probably more :-) [...] > > Consider: > > (gdb) image save FILE RANGE [FORMAT] > (gdb) image restore FILE [ADDR] > (gdb) image compare FILE [ADDR] > > where, say, RANGE could be > ADDR1 ADDR2 > "region 1" -- previously set memory region > > and FORMAT could be some bfd-supported forms like "srec" or "binary". If its a bfd-supported format such as srec, you can already use the "load" command to put it back onto the target later. Then all you have to worry about is the opposite-of-load direction.