On Jan 15, 2008 12:38 PM, Julian Seward <[EMAIL PROTECTED]> wrote:
> On Tuesday 15 January 2008 10:32, Konstantin Serebryany wrote:
> > You mean it requires 32-bit hardware? or 32-bit-only os? or 32-bit
> > executable?
>
> I _think_ requires 32-bit executable.
>
>
It looks like oprofile's callgraph requires 32-bit OS.
At least it started working for me only when I rebooted my box in 32-bit
mode.
A bit of fun: I tried to profile helgrind with vtssrun (a tool from Intel
Performance Tuning Utilities).
vtssrun EXPERIMENT_DIR -- valgrind ...
When running usual programs, vtssrun performs stack sampling of the program
and then produces nice callgraphs, flat profiles, etc.
But not for valgrind -- instead of profiling valgrind with vtssrun my
command line debugged the vtssrun utility with valgrind!!
Both tools try to inject themselves into the same address space... LOL
--kcc
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Valgrind-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
