On Saturday 09 February 2008 17:17, Bart Van Assche wrote:
> On Feb 9, 2008 3:46 PM, Julian Seward <[EMAIL PROTECTED]> wrote:
> > > I'm afraid something is wrong with one of the last commits. When I run
> > > the regression tests, on some systems all regression tests run fine
> > > and on other systems all regression tests hang.
> >
> > I did do a complete rebuild and regression test run before committing.
> > The usual cause of strangeness after changes in VEX is because the
> > dependencies are partially broken and so some stuff that should be
> > recompiled, isn't. If you make distclean and rebuild from the start,
> > does that help?
>
> After I noticed the hang, I removed the entire Valgrind directory and
> ran the commands mentioned above. That was not only a clean build, I
> also fetched the sourcecode again from the repository.
I managed to reproduce it. I think it is related to the new CPUID
info I added last night. This appears to cause glibc to loop
forever in this:
/* Query until desired cache level is enumerated. */
do
{
asm volatile ("cpuid"
: "=a" (eax), "=b" (ebx), "=c" (ecx), "=d" (edx)
: "0" (4), "2" (i++));
}
while (((eax >> 5) & 0x7) != level);
which is at glibc-2.6.1/sysdeps/x86_64/cacheinfo.c:399. Quite why
it loops there is a mystery to me given that the CPUID info that V
gives is now identical to that produced by a Core 2 CPU.
J
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Valgrind-developers mailing list
Valgrind-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
