On Sun, Jun 18, 2017 at 1:02 PM, Maxime Haselbauer <[email protected]> wrote: > I hope it is correct place to post this > > I am a bit confused on how to use valgrind inside kdevelop: > I compiled kdev-valgrind from source using the 5.1 branch (I got KDevelop > 5.1.1 KDE Neon ) > The problem is it keeps issuing the following command > > /home/max/Projects/Test_projects/testcpp> /usr/bin/valgrind --tool=callgrind > --log-socket=127.0.0.1:34555 --num-callers=12 --max-stackframe=2000000 > --error-limit=yes --cache-sim=no --branch-sim=no > --callgrind-out-file=/tmp/kdevelop.Pu7161 /usr/bin/plasmoidviewer -a . > > And I don't understand what plasmoidviewer has to do with it, since the > programm I was trying to valgrind was the following > Did I misunderstood/miss-installed something? > Best regards > > > #include <stdio.h> > #include <iostream> > #include <unistd.h> > > using namespace std; > int main(int argc, char **argv) { > int i=0; > while(i<10000000) > { > int *j=new int ; > *j=3; > i++; > std::cout<<i<<std::endl; > } > return 0; > > } >
Redirecting to kdevelop, as there might be someone there who knows. I've personally never used that plugin. Aleix
