Project Summary
The primary goal of this project 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. Some examples include: exception handling, debuggers, introspection and efficient setjmp().
In a Nutshell, libunwind...
- ...
- ...
- ...
-
...
took an estimated 28 years of effort (COCOMO model)
starting with its first commit in February, 2002
ending with its most recent commit over 2 years ago
MIT License
Permitted
Commercial Use
Modify
Distribute
Sub-License
Private Use
Forbidden
Hold Liable
Required
Include Copyright
Include License
These details are provided for information only. No information here is legal advice and should not be used as such.
Project Security
Vulnerabilities per Version ( last 10 releases )
There are no reported vulnerabilities
Project Vulnerability Report
Security Confidence Index
Vulnerability Exposure Index
Did You Know...
-
...
65% of companies leverage OSS to speed application development in 2016
-
...
by exploring contributors within projects, you can view details on every commit they have made to that project
-
...
there are over 3,000 projects on the Open Hub with security vulnerabilities reported against them
-
...
compare projects before you chose one to use
30 Day SummaryMay 26 2025 — Jun 25 2025
|
12 Month SummaryJun 25 2024 — Jun 25 2025
|
