From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28328 invoked by alias); 3 Jan 2002 09:02:52 -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 28261 invoked from network); 3 Jan 2002 09:02:45 -0000 Received: from unknown (HELO localhost.cygnus.com) (24.114.42.213) by sources.redhat.com with SMTP; 3 Jan 2002 09:02:45 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id CF62E3C44 for ; Thu, 3 Jan 2002 04:02:40 -0500 (EST) Message-ID: <3C341E2D.6050009@cygnus.com> Date: Thu, 03 Jan 2002 01:02:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.6) Gecko/20011207 X-Accept-Language: en-us MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: A copy/save command ... Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-01/txt/msg00005.txt.bz2 Hello, To toss out an idea. One of those oft mentioned missing features is a command to read/write binary data to/from GDB's target memory. There is the load command, but that works on object files (readable via BFD). Anyway, I've two vague thoughts on the syntax/semantics: 1. (gdb) copy The result of is written to the raw file. This expoits the fact that GDB stores an expression in target form in host memory. Consequently, the copy command just writes that raw data to the file. 2. (gdb) copy
or (gdb) copy/
or similar. A more traditional
/ approach. ``copy/'' comes from ``x/''. better suggestions welcome. enjoy, Andrew