On Wed, Jun 20, 2012 at 3:18 AM, Luigia Ambrosio <[email protected]>wrote:

Yes but it's not enough! I nedd the stack of the called methods and kernels. I just sent you my modified ex11 and the results of ./ex11 -log_summary

Use the debugger. Its the easiest way to get a stack. However, for the old people here, it is also possible to do by looking at the source code. Matt

thanks again

Luigia Ambrosio

Il giorno 20/giu/2012, alle ore 10:45, Aron Ahmadia ha scritto:

Have you tried passing -log_summary to the command line?

A

On Wed, Jun 20, 2012 at 11:32 AM, Luigia Ambrosio < [email protected]> wrote:

...

Hi all I'm interested in using PETSC with CUDA. I just downloaded and installed the developer version and I was testing the example #1 ($HOME/petsc-dev/src/vec/vec/examples/tutorials) to compute the norm of a vector. I would like to compare PETSC "without cuda" and "with cuda". Is there a way to profile a PETSC executable, obtain the stack of the called functions and methods and access to the function body? Can anybody make an exmple? Thanks a million

-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener