This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: corefiles/338: gcore.exp started failing
- From: mec at shout dot net
- To: gdb-prs at sources dot redhat dot com, geoffk at redhat dot com, kettenis at gnu dot org, drow at mvista dot com, nobody at sources dot redhat dot com
- Date: 18 Aug 2003 04:57:38 -0000
- Subject: Re: corefiles/338: gcore.exp started failing
- Reply-to: mec at shout dot net, gdb-prs at sources dot redhat dot com, geoffk at redhat dot com, kettenis at gnu dot org, drow at mvista dot com, nobody at sources dot redhat dot com, gdb-gnats at sources dot redhat dot com
Synopsis: gcore.exp started failing
State-Changed-From-To: open->analyzed
State-Changed-By: chastain
State-Changed-When: Mon Aug 18 04:57:38 2003
State-Changed-Why:
Oh, the joy of visiting PR's that were fixed more than a year ago!
gcore.exp is working fine with the XMM registers in gdb 5.3 and later versions.
I think Daniel fixed it with this patch:
2002-04-24 Daniel Jacobowit <drow@mvista.com>
* config/i386/tm-linux.h: Define FILL_FPXREGSET.
* gregset.h: If FILL_FPXREGSET is defined, provide
gdb_fpxregset_t, supply_fpxregset, and fill_fpxregset.
* linux-proc.c (linux_do_thread_registers): If FILL_FPXREGSET
is defined, call fpxregset.
I vouch for the test results in gdb.log: all the xmm0 register values coming up "0" in gcore.exp.
Daniel, can you take a few minutes, read the PR, and if there are no hidden gotchas, close it out?
Michael C
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=338