@Daniel: thanks - i could compile vprof now!
Jody
On Thu, Apr 23, 2009 at 12:35 PM, Daniel Spångberg wrote:
> Regarding miscompilation of vprof and bfd_get_section_size_before_reloc.
> Simply change the call from bfd_get_section_size_before_reloc to
> bdf_get_section_size in exec.cc and recompi
jody wrote:
If i get vprof or one of the other tools running, i'll write something up -
perhaps the profiling subject would be worthy for a FAQ entry...
Yes, perhaps. Note that there really are lots of options out there.
Spend a few minutes googling. There are tools, surveys of tools, et
Regarding miscompilation of vprof and bfd_get_section_size_before_reloc.
Simply change the call from bfd_get_section_size_before_reloc to
bdf_get_section_size in exec.cc and recompile.
Daniel Spångberg
Den 2009-04-23 10:16:07 skrev jody :
Hi all
Thanks for all the input.
I have not gotten
Hi all
Thanks for all the input.
I have not gotten around to try any of the tools (Sun Studio, Tau or vprof).
Actually, i can't compile vprof - make fails with
exec.cc: In static member function ‘static void
BFDExecutable::find_address_in_section(bfd*, asection*, void*)’:
exec.cc:144: error: ‘
I have used vprof, which is free, and also works well with openmpi:
http://sourceforge.net/projects/vprof/
One might need slight code modifications to get output, depending on
compilers used, such as adding
vmon_begin();
to start profiling and
vmon_done_task(rank);
to end profiling where rank
There is a tool (not free) That I have liked that works great with
OMPI, and can use gprof information.
http://www.allinea.com/index.php?page=74
Also I am not sure but Tau (which is free) Might support some gprof
hooks.
http://www.cs.uoregon.edu/research/tau/home.php
Brock Palen
www.umic
Hi,
Yes you can profile MPI applications by compiling with -pg. However, by
default each process will produce an output file called "gmon.out",
which is a problem if all processes are writing to the same global file
system (i.e. all processes will try to write to the same file).
There is an
Hi,
I've never done this, but I believe that an executable compiled with
profilling support (-pg) will generate the gmon.out file in its current
directory, regardless of running under MPI or not. So I think that
you'll have a gmon.out on each node and therefore you can "gprof" them
independent
jody wrote:
Hi
I wanted to profile my application using gprof, and proceeded like
when profiling a normal application:
- compile everything with option -pg
- run application
- call gprof
This returns a normal-looking output, but i don't know
whether this is the data for node 0 only or accumulate
Hi
I wanted to profile my application using gprof, and proceeded like
when profiling a normal application:
- compile everything with option -pg
- run application
- call gprof
This returns a normal-looking output, but i don't know
whether this is the data for node 0 only or accumulated for all nodes
10 matches
Mail list logo
