Bug#530409: marked as done (ITP: libunwind -- efficient C call-chain interface)
Your message dated Tue, 26 May 2009 23:21:10 -0700
with message-id <4A1CDBD6.3090900@inaugust.com>
and subject line Already Packaged
has caused the Debian Bug report #530409,
regarding ITP: libunwind -- efficient C call-chain interface
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
530409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530409
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Owner: Monty Taylor <mordred@inaugust.com>
Severity: wishlist
* Package name : libunwind
Version : 0.99
Upstream Author : David Mosberger <dmosberger@gmail.com>
* URL : http://www.nongnu.org/libunwind/index.html
* License : MIT
Programming Lang: C
Description : Efficient C call-chain interface
The 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. Some examples include:
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).
Monty Taylor
--- End Message ---
--- Begin Message ---
I erroneously filed this WNPP bug thinking that libunwind was not yet
packaged. It is, but only with binary packages for ia64.
--- End Message ---
Reply to: