cc_staff
256
edits
Frequently Asked Questions: Difference between revisions
Jump to navigation
Jump to search
Marked this version for translation
(Fix typo) |
(Marked this version for translation) |
||
| Line 151: | Line 151: | ||
In some instances a program which crashes or otherwise exits abnormally will leave behind a binary file, called a core file, containing a snapshot of the program's state at the moment that it crashed, typically with the extension ".core". While such files can be useful for programmers who are debugging the software in question, they are normally of no interest for regular users beyond the indication that something went wrong with the execution of the software, something already indicated by the job's output normally. You can therefore delete these files if you wish and add the line <tt>ulimit -c 0</tt> to the end of your $HOME/.bashrc file to ensure that they are no longer created. | In some instances a program which crashes or otherwise exits abnormally will leave behind a binary file, called a core file, containing a snapshot of the program's state at the moment that it crashed, typically with the extension ".core". While such files can be useful for programmers who are debugging the software in question, they are normally of no interest for regular users beyond the indication that something went wrong with the execution of the software, something already indicated by the job's output normally. You can therefore delete these files if you wish and add the line <tt>ulimit -c 0</tt> to the end of your $HOME/.bashrc file to ensure that they are no longer created. | ||
==How to fix library not found error== | ==How to fix library not found error== <!--T:54--> | ||
When installing pre-compiled binary packages in your <code>$HOME</code>, they may fail with an error such as <tt>/lib64/libc.so.6: version `GLIBC_2.18' not found</tt> at runtime. See [https://docs.computecanada.ca/wiki/Installing_software_in_your_home_directory#Installing_binary_packages Installing binary packages] for how to fix this kind of issue. | When installing pre-compiled binary packages in your <code>$HOME</code>, they may fail with an error such as <tt>/lib64/libc.so.6: version `GLIBC_2.18' not found</tt> at runtime. See [https://docs.computecanada.ca/wiki/Installing_software_in_your_home_directory#Installing_binary_packages Installing binary packages] for how to fix this kind of issue. | ||
</translate> | </translate> | ||