From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: yao@codesourcery.com (Yao Qi), anton@samba.org
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Detect 64-bit-ness in PowerPC Book III-E
Date: Thu, 11 Dec 2014 15:31:00 -0000 [thread overview]
Message-ID: <201412111530.sBBFUxsi023697@d03av02.boulder.ibm.com> (raw)
In-Reply-To: <1418296515-8689-1-git-send-email-yao@codesourcery.com> from "Yao Qi" at Dec 11, 2014 07:15:15 PM
Yao Qi wrote:
> This patch is to teach GDBServer to detect 64-bit inferior correctly.
> We find a problem that GDBServer is unable to detect on an e5500 core
> processor. Current GDBServer assumes that MSR is a 64-bit register,
> but MSR is a 32-bit register in Book III-E. This patch is to fix this
> problem by checking both bits in MSR, in order to handle both Book
> III-S and Book III-E.
Hmm. If it actually is Book III-S, then bit 32 is "reserved", so I'm
not sure including it in the check is safe.
Anton, what would you suggest a user program to use to safely detect
whether a ptrace-attached child is 64-bit or not, on either Book III-S
or Book III-E systems?
In any case, whatever we do, we should do both in native GDB and
gdbserver.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2014-12-11 15:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 11:15 Yao Qi
2014-12-11 15:31 ` Ulrich Weigand [this message]
2014-12-19 8:06 ` Yao Qi
2014-12-19 15:49 ` Ulrich Weigand
2015-01-11 8:27 ` [PATCH 0/2, V2] " Yao Qi
2015-01-11 8:27 ` [PATCH 1/2] Move some ppc macros to nat/ppc-linux.h Yao Qi
2015-01-13 16:57 ` Ulrich Weigand
2015-01-11 8:27 ` [PATCH 2/2] Detect 64-bit-ness in PowerPC Book III-E Yao Qi
2015-01-13 17:00 ` Ulrich Weigand
2015-01-14 2:54 ` Yao Qi
2015-01-14 12:47 ` Ulrich Weigand
2015-01-14 14:22 ` Yao Qi
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=201412111530.sBBFUxsi023697@d03av02.boulder.ibm.com \
--to=uweigand@de.ibm.com \
--cc=anton@samba.org \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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