search for: currentpath

...nvention. ## ## 1. The testSuite files and test files should be in the same directory like this example. ## ## 2. Always include the following five objects in your own test file ## as it is shown in this example and modify them as you want. ## (-> pathToCode, codeFileName, currentPath, .setUp, .tearDown) ## ## 3. Then, properly change the pathToCode and the codeFileName. ## You can add your own codes to .setUP and .tearDown. ## ## 4. Use one test file for each code file. This is a good practice. ## ################################################## pathToCode <-...

...eInfo>(); for(Module::iterator F = M.begin();F != M.end(); ++F){ if (F->isDeclaration()) continue; pathProfileInfo.setCurrentFunction(F); for(ProfilePathIterator nextPath=pathProfileInfo.pathBegin();nextPath != pathProfileInfo.pathEnd();nextPath++){ ProfilePath* currentPath = nextPath->second; errs() << "Function: "+ F->getName() << "\n"; errs() <<"path #" << currentPath->getNumber()<<":" << currentPath->getCount() <<"\n"; } } return true; }...