There is a newer version of libunwindThe primary goal of libunwind is to define a portable and efficient C programming interface (API) to determine the call-chain of a program. The API additionally provides the means to manipulate the preserved (callee-saved) state of each call-frame and to resume execution at any point in the call-chain (non-local goto). The API supports both local (same-process) and remote (across-process) operation. As such, the API is useful in a number of applications
Accessing libunwind 1.4.0-GCCcore-10.2.0
To load the module for libunwind 1.4.0-GCCcore-10.2.0 please use this command on the BEAR systems (BlueBEAR, BEARCloud VMs, and CaStLeS VMs):
module load libunwind/1.4.0-GCCcore-10.2.0
BEAR Apps Version
EL8-cascadelake — EL8-haswell — Ubuntu20.04-haswell
The listed architectures consist of two part: OS-CPU.
- BlueBEAR: The OS used on BlueBEAR is represented by EL and there are several different processor (CPU) types available on BlueBEAR. More information about the processor types on BlueBEAR is available on the BlueBEAR Job Submission page.
- BEAR and CaStLeS Cloud VMs: These VMs can have one of two OSes. Those with access to a BEAR Cloud or CaStLeS VM should check that the listed architectures for an application include the OS of VM being used. The VMs, irrespective of OS, will use the haswell CPU type.
For more information visit the libunwind website.
This version of libunwind has a direct dependency on: GCCcore/10.2.0 XZ/5.2.5-GCCcore-10.2.0
This version of libunwind is a direct dependent of: GStreamer/1.18.4-GCC-10.2.0 Mesa/20.2.1-GCCcore-10.2.0 Mesa/20.2.1-GCCcore-10.2.0-libpng-1.2.58-dri Xvfb/1.20.9-GCCcore-10.2.0
These versions of libunwind are available on the BEAR systems (BlueBEAR, BEARCloud VMs, and CaStLeS VMs). These will be retained in accordance with our Applications Support and Retention Policy.
|Version||BEAR Apps Version|
Last modified on 22nd February 2021