yade-dev team mailing list archive

[Bruno Chareyre <bruno.chareyre@xxxxxxxxxxx>]

Václav Šmilauer a écrit :
>> That is true : valgrind shows only one call to "new" in 100k iterations.
>> Time is spent in another function that I can't identify (named 
>> "0x000F..."), probably because it is a macro, an inlined function, or 
>> something like that.
>>   
>>     
> That is a library function (boost, libstdc++, ...?) and the library was
> compiled without debugging symbols. If a function is inlined, it is not
> a separate function but the compiler inserts the code at that place
> where called (hence valgrind would attribute it to the caller). The same
> with macros, where preprocessor inserts the program text at the place
> where used.
>
>   
Problem is vallgrind see this 0x00.. as a function of 
libBodyMacroParameters.so, does it make sense for you?



-- 
 
_______________
Chareyre Bruno
Maitre de conference

Institut National Polytechnique de Grenoble
Laboratoire 3S (Soils Solids Structures) - bureau E145
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
________________

_______________________________________________
yade-dev mailing list
yade-dev@xxxxxxxxxxxxxxxx
https://lists.berlios.de/mailman/listinfo/yade-dev