Date: Wed, 22 Apr 2020 14:25:51 +0000 (UTC) From: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org> To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r532478 - head/devel/libunwind Message-ID: <202004221425.03MEPpYB006570@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202004221425.03MEPpYB006570>