|
From: Tom H. <th...@cy...> - 2004-12-15 00:02:53
|
In message <41B...@wm...>
Betty Wang <tx...@wm...> wrote:
> I modified Valgrind's Cachegrind a little. When I run my own version of
> Cachegrind on some OMP benchmark, I got the following warning:
>
>
> ==15149== warning: Valgrind's pthread_getattr_np is incomplete
> ==15149== your program may misbehave as a result
> ==15149== warning: Valgrind's pthread_attr_destroy does nothing
> ==15149== your program may misbehave as a result
>
> Running Cachegrind on the same benchmark some weeks ago, I don't
> remember this warning showed up before. Could anybody give me some clue
> of where to look in Valgrind in order to get rid of this warning?
Why? Is is causing you a problem? I believe getattr_np is fairly
complete now although some things may be missing. I don't think
that destroy is likely to cause any problems beyond a possible
minor memory leak. I'm not even sure about that - aren't the
attribute structures allocated by the caller?
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|