From: Daniel Jacobowitz <drow@false.org>
To: Manoj Iyer <manjo@austin.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] gdb.server testcases (resend)
Date: Wed, 18 May 2005 18:08:00 -0000 [thread overview]
Message-ID: <20050518160144.GA9283@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0505181034560.5124@lazy>
On Wed, May 18, 2005 at 10:37:56AM -0500, Manoj Iyer wrote:
>
> Daniel,
>
> The patches did not apply cleanly to mainline, so I had to hand patch the
> files. Also, in the final link stage for gdbserver ld complained that:
>
> /usr/bin/ld: warning: powerpc:common64 architecture of input file
> `inferiors.o' is incompatible with powerpc:common output
>
> so I had to add a -m64 to the linker call.
>
> gdbserver still broken:.
>
> $ ./gdbserver uranus.ltc.austin.ibm.com /tmp/server
> Process /tmp/server created; pid = 4747
> reading register 70: Input/output error
> Exiting
My reading of the kernel source suggests that FPSCR should be accessible
using that address. You should figure out why it isn't.
At a guess your headers are broken:
/* NOTE: cagney/2005-02-08: On some 64-bit GNU/Linux systems the
kernel headers incorrectly contained the 32-bit definition of
PT_FPSCR. For the 32-bit definition, floating-point
registers occupy two 32-bit "slots", and the FPSCR lives in
the secondhalf of such a slot-pair (hence +1). For 64-bit,
the FPSCR instead occupies the full 64-bit 2-word-slot and
hence no adjustment is necessary. Hack around this. */
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-18 16:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 2:38 Manoj Iyer
2005-05-17 19:02 ` Manoj Iyer
2005-05-18 1:45 ` Daniel Jacobowitz
2005-05-18 9:52 ` Manoj Iyer
2005-05-18 16:01 ` Daniel Jacobowitz
2005-05-18 16:29 ` Manoj Iyer
2005-05-18 18:08 ` Daniel Jacobowitz [this message]
2005-05-18 22:08 ` Manoj Iyer
2005-05-19 14:46 Wu Zhou
2005-05-19 17:52 ` Manoj Iyer
2005-05-22 20:40 ` Daniel Jacobowitz
2005-05-22 21:01 ` Daniel Jacobowitz
2005-05-23 11:21 ` Wu Zhou
2005-05-23 18:26 ` Daniel Jacobowitz
2005-05-24 4:17 ` Wu Zhou
2005-05-24 8:29 ` Daniel Jacobowitz
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=20050518160144.GA9283@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=manjo@austin.ibm.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