From: "Slater, Joseph" <joe.slater@windriver.com>
To: <gdb@sources.redhat.com>
Subject: MIPS-64 gdb to kgdb almost working
Date: Wed, 28 Sep 2005 23:14:00 -0000 [thread overview]
Message-ID: <8566118CD734444C9C07C21F5A11A676EB8408@ALA-MAIL03.corp.ad.wrs.com> (raw)
Hi,
I am trying to connect gdb via kgdboe to a mips-64 Broadcom target
running a 2.6.10 kernel. Things actually work (sort of) except that gdb
seems to believe pointers are 32-bits. Usually, that is, because if it
hits a breakpoint is displays a 64-bit address. But, if I print the
address of something, it comes out as a 32-bit value.
It also knows the registers are 64-bits, but it only picks out and
displays every other 4 byte chunk in the stream sent to it by kgdb.
All the memory access requests to kgdb have 4 byte addresses, and ask
for 4 bytes to be read.
BTW, the way I got it to work is to or 0xffffffff00000000 into all the
addresses before accessing them with kgdb. This works because our
kernel address space seems to start at 0xffffffff80000000.
It seems close enough to working that there should be a "trivial" fix.
Does anybody know of one?
Joe
reply other threads:[~2005-09-28 23:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8566118CD734444C9C07C21F5A11A676EB8408@ALA-MAIL03.corp.ad.wrs.com \
--to=joe.slater@windriver.com \
--cc=gdb@sources.redhat.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).