Hi all, I am having an issue with callgrind tool. I am using the valgrind --version: *valgrind-3.1.1* in 32 bit red-hat Linux environment.
My program is basically document analyzer. What it does is, process the input document and give the result. I just want to analyze my program with callgrind (purpose is to reduce the "new" operator calls). The callgrind tool is perfect for it, with small number of documents, but it is giving problems with large number of documents. For example, the callgrind output is OK for around 200 documents. But I want to do the same analyzes with more than 1000 documents. In that case the callgrind report most of the functions as "*cycle*" even the *new *and *malloc *calls. *operator new <cycle 2> malloc <cycle 2> free <cycle 2>* [image: sample callgrind outpu.png] And also it does not show the call flows correctly. This can not happen due to an error in my program, Because it still (even after 1000 documents) work perfectly with giving the expected outputs. What could be the reason for this....?? Is this due to the large number of calls (exceeding the supported maximum numeric limits ). The following data may be help to identify the issue. For 200 documents - new operator has called 31,452,352 - malloc has called 31,468,098. For around 1000 documents the - new operator has called 1,003,897,109 - malloc has called 1,004,566,498 -- Regards, R. P. Janaka
<<sample callgrind outpu.png>>
------------------------------------------------------------------------------
_______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
