11debugging_tools.doxy 2.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
  1. /*
  2. * This file is part of the StarPU Handbook.
  3. * Copyright (C) 2009--2011 Universit@'e de Bordeaux 1
  4. * Copyright (C) 2010, 2011, 2012, 2013, 2014 Centre National de la Recherche Scientifique
  5. * Copyright (C) 2011, 2012 Institut National de Recherche en Informatique et Automatique
  6. * See the file version.doxy for copying conditions.
  7. */
  8. /*! \page DebuggingTools Debugging Tools
  9. StarPU provides several tools to help debugging applications. Execution traces
  10. can be generated and displayed graphically, see \ref
  11. GeneratingTracesWithFxT.
  12. Some gdb helpers are also provided to show the whole StarPU state:
  13. \verbatim
  14. (gdb) source tools/gdbinit
  15. (gdb) help starpu
  16. \endverbatim
  17. Valgrind can be used on StarPU: valgrind.h just needs to be found at ./configure
  18. time, to tell valgrind about some known false positives and disable host memory
  19. pinning.
  20. The STARPU_DISABLE_KERNELS environment variable can also be set to 1 to make
  21. StarPU do everything (schedule tasks, transfer memory, etc.) except actually
  22. calling the application-provided kernel functions, i.e. the computation will not
  23. happen. This permits to quickly check that the task scheme is working properly.
  24. The Temanejo task debugger can also be used, see \ref UsingTheTemanejoTaskDebugger.
  25. \section UsingTheTemanejoTaskDebugger Using The Temanejo Task Debugger
  26. StarPU can connect to Temanejo >= 1.0rc2 (see
  27. http://www.hlrs.de/temanejo), to permit
  28. nice visual task debugging. To do so, build Temanejo's <c>libayudame.so</c>,
  29. install <c>Ayudame.h</c> to e.g. <c>/usr/local/include</c>, apply the
  30. <c>tools/patch-ayudame</c> to it to fix C build, re-<c>./configure</c>, make
  31. sure that it found it, rebuild StarPU. Run the Temanejo GUI, give it the path
  32. to your application, any options you want to pass it, the path to <c>libayudame.so</c>.
  33. Make sure to specify at least the same number of CPUs in the dialog box as your
  34. machine has, otherwise an error will happen during execution. Future versions
  35. of Temanejo should be able to tell StarPU the number of CPUs to use.
  36. Tag numbers have to be below <c>4000000000000000000ULL</c> to be usable for
  37. Temanejo (so as to distinguish them from tasks).
  38. */