This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/338: gcore.exp started failing
- From: geoffk at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Cc: Mark Kettenis <kettenis at gnu dot org>
- Date: 4 Feb 2002 17:26:21 -0000
- Subject: gdb/338: gcore.exp started failing
- Reply-to: geoffk at redhat dot com
>Number: 338
>Category: gdb
>Synopsis: gcore.exp started failing
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Feb 04 10:58:04 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: geoffk@redhat.com
>Release: 2002-02-02-cvs
>Organization:
>Environment:
Red Hat Linux 7; latest CVS binutils and GCC as of 2002-02-02.
Pentium III.
>Description:
Sometime between 20020114T042927Z and 20020118080805Z,
gcore.exp started failing on x86-linux. The symptom is that
after loading the core file, the XMM registers print as
xmm0 {f = {0x0, 0x0, 0x0, 0x0}} {f = {-nan(0x7fffff), -nan(0x7fffff), -nan(0x7fffff), -nan(0x7fffff)}}
rather than
xmm0 {f = {0x0, 0x0, 0x0, 0x0}} {f = {0, 0, 0, 0}}
the second is the historical behaviour.
>How-To-Repeat:
make check
>Fix:
I suspect this change:
2002-01-19 Mark Kettenis <kettenis@gnu.org>
* i386gnu-nat.c: Include "i386-tdep.h".
(fetch_fpregs): Simplify code dealing with uninitialized floating
point states such that it doesn't require FP7_REGNUM.
but have not tried backing it out to see if the problem goes away.
>Release-Note:
>Audit-Trail:
>Unformatted: