From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32252 invoked by alias); 6 Jun 2003 21:18:55 -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 32206 invoked from network); 6 Jun 2003 21:18:54 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.131) by sources.redhat.com with SMTP; 6 Jun 2003 21:18:54 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id B09E72B5F; Fri, 6 Jun 2003 17:18:41 -0400 (EDT) Message-ID: <3EE10531.4030403@redhat.com> Date: Fri, 06 Jun 2003 21:18:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: #-sadiq shaikh-# Cc: gdb@sources.redhat.com Subject: Re: How gdb support 32 & 64 bit value ? References: <20030606133248.39558.qmail@web41807.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-06/txt/msg00086.txt.bz2 > Hi, > > Can anybody tell me that where exactly in the code(gdb-5.3), > gdb is converting/interpreting 32 bit value into 64 bit value. > Actaully in my case(target MIPS 32 bit). > gdbserver is sending client 32 bit values but at the client > end he is treating/holding in 64 bit value.Moreover treating > is as signed like 0xffffffff80f60050 instead of 0x0000000080f60050 FYI, MIPS has signed addresses, so any 32 bit value converted to 64 bits must be sign extended. Hence the value 0xffffffff80f60050 isn't unexpected. You can force GDB to think it is 32 bit by either building a 32 bit GDB or forcing the architecture to 32 bits (set architecture mips). However, that may not work with your remote target. Andrew