From: Andrew Cagney <ac131313@redhat.com>
To: #-sadiq shaikh-# <saadiqshaikh@yahoo.com>
Cc: gdb@sources.redhat.com
Subject: Re: How gdb support 32 & 64 bit value ?
Date: Fri, 06 Jun 2003 21:18:00 -0000 [thread overview]
Message-ID: <3EE10531.4030403@redhat.com> (raw)
In-Reply-To: <20030606133248.39558.qmail@web41807.mail.yahoo.com>
> 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
prev parent reply other threads:[~2003-06-06 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 13:32 #-sadiq shaikh-#
2003-06-06 21:18 ` Andrew Cagney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EE10531.4030403@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=saadiqshaikh@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).