On Mon, 11 Mar 2013, Ron wrote: > I cannot run valgrind anymore together with a Gambas3 project to check > memory alloc issues. > > I use this syntax inside the project directory: > > $ gbc3 -agpmt > $ valgrind --log-file=/tmp/valgrind.log --tool=memcheck --num-callers=50 gbx3 > -p > > But then I end up in this: > > Welcome to the Gambas debugger. > * ? > > > > Did I miss something? >
According to "gbx3 --help", this is the intended behaviour for the -p switch you gave: "activate profiling and debugging mode" and you got dropped into debug mode apparently. Regards, Tobi ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
