Hi janjust,
> I found that perftools-lite do not support static
> linking (kinda odd).
> There are no perf.a files to be linked statically with valgrind; however,
> perftools should work with static linking.
>
> The perftools process is:
> build your application and retain object files, then use
Hi John,
Thanks for the reply. I found that perftools-lite do not support static
linking (kinda odd).
There are no perf.a files to be linked statically with valgrind; however,
perftools should work with static linking.
The perftools process is:
build your application and retain object files, then
>
> Dear Sir,
>
> Thank you for replying but aprof i guess is like a
> profiler, what i am looking for is a code or tool that takes any c or c++
> program and on execution gives me the output in terms of asymptotic
> notation.
>
> For example : test.c
> for (i =
On 04/07/2014 02:47 PM, Vijay Viswanathan wrote:
>
> I ran myprogram using :
>
> G_SLICE=always-malloc valgrind -v --run-libc-freeres=no --vgdb=no
> --tool=memcheck --leak-check=full --leak-resolution=high --num-callers=50
> --workaround-gcc296-bugs=yes --log-f
> ile=vgdump
>
> I got this outp
On 04/07/2014 10:26 PM, Bob Kuo wrote:
> Is it possible to run valgrind *without* the debug symbols available
> and then take the valgrind log output, the .map, and the debug symbols
> to get a full stack trace? That would simplify our testing greatly.
In theory you might be able to use addr2line
I ran myprogram using :
G_SLICE=always-malloc valgrind -v --run-libc-freeres=no --vgdb=no
--tool=memcheck --leak-check=full --leak-resolution=high --num-callers=50
--workaround-gcc296-bugs=yes --log-f
ile=vgdump
I got this output :
mypgrogram:64: can't map '/etc/ld.so.cache'
Any idea whats goi
Hello valgrind-users,
We are currently using valgrind at work by putting the debug symbols onto the
appliance at test time and running our process under valgrind. The log output
contains the correct stack trace as expected. Setting up the appliance for
this kind of testing is non-trivial, es
