|
From: Matt D. <da...@qu...> - 2003-08-09 09:20:15
|
Hi Guys, I have been using valgrind for a while and I have been very happy. I am now running valgrind on RedHat 9.0 and have been having some problems. I have read that there are some problems with RedHat 9.0 in the FAQ. Is this (see below) one of them? Kind Regards, Matt -- 192/2[1] matt ocview $ valgrind bin/ocview ==17544== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux. ==17544== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward. ==17544== Using valgrind-20030725, a program supervision framework for x86-linux. ==17544== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward. ==17544== Estimated CPU clock rate is 2667 MHz ==17544== For more details, rerun with: -v ==17544== Memcheck: mc_translate.c:1091 (memcheck_instrument): Assertion `u_in->size == 4 || u_in->size == 16' failed. sched status: Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 ==17544== at 0x42130171: __static_initialization_and_destruction_0(int, int) (in /usr/local/stow/OpenCascade-5.0/lib/libTKTopAlgo.so.0.0.0) ==17544== by 0x42131583: _GLOBAL__I__ZN16BRepGProp_VinertC2Ev (in /usr/local/stow/OpenCascade-5.0/lib/libTKTopAlgo.so.0.0.0) ==17544== by 0x422CD084: (within /usr/local/stow/OpenCascade-5.0/lib/libTKTopAlgo.so.0.0.0) ==17544== by 0x420A6EB8: (within /usr/local/stow/OpenCascade-5.0/lib/libTKTopAlgo.so.0.0.0) Note: see also the FAQ.txt in the source distribution. It contains workarounds to several common problems. If that doesn't help, please report this bug to: js...@ac... In the bug report, send all the above text, the valgrind version, and what Linux distro you are using. Thanks. -- Matt Davies <da...@ac...> |
|
From: Tom H. <th...@cy...> - 2003-08-09 12:26:28
|
In message <106...@sh...>
Matt Davies <da...@qu...> wrote:
> I am now running valgrind on RedHat 9.0 and have been having some
> problems. I have read that there are some problems with RedHat 9.0 in
> the FAQ. Is this (see below) one of them?
That assertion is in memcheck's SSE translation logic because it
saw a UInstr with an unexpected size. Presumably it's a corner of
the SSE instruction set that memcheck doesn't know about yet.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|