svn commit: r532478 - head/devel/libunwind
Sunpoet Po-Chuan Hsieh
sunpoet at FreeBSD.org
Wed Apr 22 14:25:52 UTC 2020
Author: sunpoet
Date: Wed Apr 22 14:25:51 2020
New Revision: 532478
URL: https://svnweb.freebsd.org/changeset/ports/532478
Log:
Update pkg-descr and WWW
Modified:
head/devel/libunwind/pkg-descr
Modified: head/devel/libunwind/pkg-descr
==============================================================================
--- head/devel/libunwind/pkg-descr Wed Apr 22 14:20:41 2020 (r532477)
+++ head/devel/libunwind/pkg-descr Wed Apr 22 14:25:51 2020 (r532478)
@@ -1,24 +1,24 @@
-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:
+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:
-o exception handling
- The libunwind API makes it trivial to implement the stack-manipulation
- aspects of exception handling.
-o debuggers
- The libunwind API makes it trivial for debuggers to generate
- the call-chain (backtrace) of the threads in a running program.
-o introspection
- It is often useful for a running thread to determine its call-chain.
- For example, this is useful to display error messages (to show how
- the error came about) and for performance monitoring/analysis.
-o efficient setjmp()
- With libunwind, it is possible to implement an extremely efficient
- version of setjmp(). Effectively, the only context that needs to be
- saved consists of the stack-pointer(s).
+- exception handling
+ The libunwind API makes it trivial to implement the stack-manipulation aspects
+ of exception handling.
+- debuggers
+ The libunwind API makes it trivial for debuggers to generate the call-chain
+ (backtrace) of the threads in a running program.
+- introspection
+ It is often useful for a running thread to determine its call-chain. For
+ example, this is useful to display error messages (to show how the error came
+ about) and for performance monitoring/analysis.
+- efficient setjmp()
+ With libunwind, it is possible to implement an extremely efficient version of
+ setjmp(). Effectively, the only context that needs to be saved consists of the
+ stack-pointer(s).
-WWW: http://www.nongnu.org/libunwind/
+WWW: https://www.nongnu.org/libunwind/
More information about the svn-ports-all
mailing list