Bureaucrats, cc_docs_admin, cc_staff
2,314
edits
Valgrind: Difference between revisions
Jump to navigation
Jump to search
Marked this version for translation
(Marked this version for translation) |
|||
| Line 7: | Line 7: | ||
[http://valgrind.org/ Valgrind] is a powerful debugging tool to detect bad memory usage. It can detect memory leaks, but also access to unallocated or deallocated memory, multiple deallocation or other bad memory usage. If your program ends with a ''segmentation fault'', ''broken pipe'' or ''bus error'', you most likely have such a problem in your code. Valgrind is installed on Compute Canada clusters as part of the base software distribution, so there is no need to load a module to use it. | [http://valgrind.org/ Valgrind] is a powerful debugging tool to detect bad memory usage. It can detect memory leaks, but also access to unallocated or deallocated memory, multiple deallocation or other bad memory usage. If your program ends with a ''segmentation fault'', ''broken pipe'' or ''bus error'', you most likely have such a problem in your code. Valgrind is installed on Compute Canada clusters as part of the base software distribution, so there is no need to load a module to use it. | ||
== AVX-512 Limitations == | == AVX-512 Limitations == <!--T:12--> | ||
Note that current versions of Valgrind are unable to handle the [https://en.wikipedia.org/wiki/AVX-512 AVX-512] instructions used on the latest Intel processors, producing an error message like the following, | Note that current versions of Valgrind are unable to handle the [https://en.wikipedia.org/wiki/AVX-512 AVX-512] instructions used on the latest Intel processors, producing an error message like the following, | ||
</translate> | </translate> | ||
| Line 21: | Line 21: | ||
</source> | </source> | ||
<translate> | <translate> | ||
<!--T:13--> | |||
Note that on [[Béluga]], the default environment uses these AVX-512 instructions. You can circumvent this problem by | Note that on [[Béluga]], the default environment uses these AVX-512 instructions. You can circumvent this problem by | ||
first loading the AVX-2 environment, | first loading the AVX-2 environment, | ||