From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11613 invoked by alias); 4 Nov 2002 16:41:20 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 11548 invoked from network); 4 Nov 2002 16:41:19 -0000 Received: from unknown (HELO lizzard.sbs.de) (194.138.37.39) by sources.redhat.com with SMTP; 4 Nov 2002 16:41:19 -0000 Received: from mail.fth.sbs.de (mail.fth.sbs.de [192.129.41.35]) by lizzard.sbs.de (8.11.6/8.11.6) with ESMTP id gA4GfIN19693 for ; Mon, 4 Nov 2002 17:41:18 +0100 (MET) Received: from nsprim.swb.siemens.de (nsprim.swb.siemens.de [141.73.80.3]) by mail.fth.sbs.de (8.11.6/8.11.6) with ESMTP id gA4GfHE11608 for ; Mon, 4 Nov 2002 17:41:18 +0100 (MET) Received: from fiji.swb.siemens.de (fiji.swb.siemens.de [141.73.80.26]) by nsprim.swb.siemens.de (8.9.1/8.9.1) with ESMTP id RAA24835 for ; Mon, 4 Nov 2002 17:41:14 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by fiji.swb.siemens.de (8.10.2+Sun/8.10.2) with SMTP id gA4GfFD07597; Mon, 4 Nov 2002 17:41:15 +0100 (MET) Message-Id: <200211041641.gA4GfFD07597@fiji.swb.siemens.de> Date: Mon, 04 Nov 2002 08:41:00 -0000 From: Ruppert Reply-To: Ruppert Subject: memory window: bug wrt endianness To: insight@sources.redhat.com Cc: ru@swb.siemens.de MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: ZaKbCjBrqhMGOpWufyTk7Q== X-SW-Source: 2002-q4/txt/msg00070.txt.bz2 Hi, I think I found a bug with the implementation of the memory window in insight-5.1: values written to memory from the memory window are written with the wrong endianness (at least in the "word" representation of the window). This was observed on a Suse Linux system with insight-5.1 installed. Consider the following trivial program: #include int i = 1; int main() { printf("Hello World: %d\n",i); return 0; } At a breakpoint at the printf statement, I get in a console window: (gdb) p i $1 = 1 (gdb) p &i $2 = (int *) 0x8049518 When I open the memory window, it displays 0x00000001 in the field which corresponds to address 0x8049518. Then I click into this field, change this to 0x00000002 and press Enter. The field continues to display 0x00000002. When I scroll up or down in the memory window the contents of this field suddenly changes to 0x02000000. This value appears also in the console window: (gdb) p /x i $3 = 0x2000000 >From this I conclude that the "memory write" from the memory window in insight-5.1 has written the value of i with the wrong endianness. This can also be seen when I change the "size" preference to "Byte": the value "2" was written to 0x804951b and not to 0x8049518. I could myself do some debugging, so: Could anybody give me a hint where to look for the reason for this ? ------------------- Regards Dieter Ruppert RTS GmbH ru@swb.siemens.de