From: Mark Kettenis <kettenis@science.uva.nl>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Felix.Buenemann@gmx.de, gdb-patches@sourceware.cygnus.com
Subject: Re: current CVS gdb and SSE xmm registers don't work
Date: Mon, 16 Jul 2001 06:01:00 -0000 [thread overview]
Message-ID: <s3iy9ppghb8.fsf@debye.wins.uva.nl> (raw)
In-Reply-To: <3B51F509.3040704@cygnus.com>
Andrew Cagney <ac131313@cygnus.com> writes:
> > Hi,
> >
> > with current gdb+dejagnu (1day old) and also gdb from 20010622, displaying of
> > the Pentium IIIs SSE registers in gdb doesn't work correct anymore, when I do
> > for example print $xmm0 all 4 values displayed are -NaN (always, even
> > directly after loading data into that register).
> > I'm using Linux 2.4.4 kernel with suse patches, compiled for PIII, gcc 2.95.3
> > and glibc 2.2. Software I debugged was compiled with -g3 compilerflag.
> >
> > This is what it looks like:
> > (gdb) print $xmm0
> > $12 = {f = {-nan(0x7fffff), -nan(0x7fffff), -nan(0x7fffff), -nan(0x7fffff)}}
> >
> > I know that it worked with older snapshot from around april/may 2001, but
> > I've deleted that one :(
> > -- Best Regards, Felix
>
>
> What happens if you use gdb/i387-tdep.c version 1.9 instead of 1.12?
> Sounds like my ``tweek'' may still be breaking it :-/
I don't think your tweek has anything to do with it Andrew. From the
information Felix provides, I conclude that somehow a
PTRACE_GETFPXREGS request is failing (see
i386-linux-nat.c:fetch_fpxregs()). Therefore I would suspect this to
be a kernel bug, or misconfiguration. Felix, can debug GDB itself
(using GDB :-)) and see why that particular ptrace call is failing? I
cannot do this myself, since I don't have a PIII.
Mark
next prev parent reply other threads:[~2001-07-16 6:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01071511090404.13471@astral>
2001-07-15 12:54 ` Andrew Cagney
2001-07-16 6:01 ` Mark Kettenis [this message]
2001-07-16 12:32 Felix Buenemann
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=s3iy9ppghb8.fsf@debye.wins.uva.nl \
--to=kettenis@science.uva.nl \
--cc=Felix.Buenemann@gmx.de \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.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