From: "Dave Korn" <dave.korn@artimi.com>
To: "'Vladimir Prus'" <ghost@cs.msu.su>, <gdb@sources.redhat.com>
Subject: RE: Targets with non-byte-addressable memory
Date: Fri, 23 Sep 2005 17:12:00 -0000 [thread overview]
Message-ID: <SERRANORNZSPGNkY5Te00000236@SERRANO.CAM.ARTIMI.COM> (raw)
In-Reply-To: <dh0fuj$2nu$1@sea.gmane.org>
----Original Message----
>From: Vladimir Prus
>Sent: 23 September 2005 09:56
> Hello!
>
> Does anybody has experience of porting gdb to a target where memory is not
> byte-addressable. That is, if you read 0x80000007 you get 4 bytes and if
> you read 0x80000008 you get another 4 bytes.
>
> The source has TARGET_CHAR_BIT macro, but no target under "config" makes
> use of them which makes me suspect that setting it won't do any good. In
> fact, after setting it to 32, I get compile error in ax-gdb.c:
>
> case 8 / TARGET_CHAR_BIT:
> ax_simple (ax, aop_ref8);
> break;
> case 16 / TARGET_CHAR_BIT:
> ax_simple (ax, aop_ref16);
> break;
> case 32 / TARGET_CHAR_BIT:
> ax_simple (ax, aop_ref32);
> break;
> case 64 / TARGET_CHAR_BIT:
> ax_simple (ax, aop_ref64);
>
> as both 8/32 and 16/32 give 0, and I get duplicate case label.
Changing TARGET_CHAR_BIT is the wrong way to go. Basically, IIUIC, you
shouldn't need to do anything at all for native debugging, and for remote
debugging, you'll have to take care of it in the stub/server.
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2005-09-23 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 8:59 Vladimir Prus
2005-09-23 17:12 ` Dave Korn [this message]
2005-09-26 6:13 ` Vladimir Prus
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=SERRANORNZSPGNkY5Te00000236@SERRANO.CAM.ARTIMI.COM \
--to=dave.korn@artimi.com \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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).