From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14956 invoked by alias); 16 Jun 2009 07:40:09 -0000 Received: (qmail 14946 invoked by uid 22791); 16 Jun 2009 07:40:08 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp.nokia.com (HELO mgw-mx06.nokia.com) (192.100.122.233) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 16 Jun 2009 07:40:03 +0000 Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n5G7daaI005279 for ; Tue, 16 Jun 2009 10:39:52 +0300 Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Jun 2009 10:39:07 +0300 Received: from mgw-da01.ext.nokia.com ([147.243.128.24]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Jun 2009 10:39:05 +0300 Received: from gar.localnet (bettdhcp167194.europe.nokia.com [172.25.167.194]) by mgw-da01.ext.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n5G7d1bi002030 for ; Tue, 16 Jun 2009 10:39:02 +0300 From: =?iso-8859-1?q?Andr=E9_P=F6nitz?= To: gdb@sourceware.org Subject: Re: how to r/w memory Date: Tue, 16 Jun 2009 07:40:00 -0000 User-Agent: KMail/1.11.2 (Linux/2.6.28-11-generic; KDE/4.2.2; i686; ; ) References: <3a665c760906152247r1625a2ban876c8c55ab52d4e2@mail.gmail.com> In-Reply-To: <3a665c760906152247r1625a2ban876c8c55ab52d4e2@mail.gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906160939.18287.andre.poenitz@nokia.com> X-Nokia-AV: Clean Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-06/txt/msg00172.txt.bz2 On Tuesday 16 June 2009 07:47:50 loody wrote: > Dear all: > From the gdb document, we can use "x/nfu address" to read memory, but > how we can write it? > I have tried "x 0x80000000=0" like "p var=val" but it fail. > thanks for your help, > miloody I use set {char[5]} &buffer = {65,66,67,68,69} I am not sure it's the recommended approach but "works". Andre'