tools-dev] Gcov and Gprof plugins
Hi,
You're right, it makes sense.
It was not the way taken at the origin, but it can be changed.
Note that at the origin , this plugin was developed in STMicroelectronics for a
cross-development environment.
Gprof and gcov plugins depends on cross-b
Hi,
You're right, it makes sense.
It was not the way taken at the origin, but it can be changed.
Note that at the origin , this plugin was developed in STMicroelectronics
for a cross-development environment.
Gprof and gcov plugins depends on cross-binutils to read the binary file.
An extension po
On 06/18/2012 05:39 PM, Renato Stoffalette Joao wrote:
On Mon, 2012-06-18 at 17:09 -0400, Jeff Johnston wrote:
Gprof and gcov get their data just by running the executable that has
been compiled and linked with special compiler options.
Valgrind and Oprofile have executables that must run (Valg
On Mon, 2012-06-18 at 17:09 -0400, Jeff Johnston wrote:
> Gprof and gcov get their data just by running the executable that has
> been compiled and linked with special compiler options.
>
> Valgrind and Oprofile have executables that must run (Valgind itself and
> opcontrol).
>
Ok, I understand
Gprof and gcov get their data just by running the executable that has
been compiled and linked with special compiler options.
Valgrind and Oprofile have executables that must run (Valgind itself and
opcontrol).
The plug-ins were written by separate developers so I would call the
difference a pro
