Bug 703159

Summary: Please ship libunwind-ptrace.a
Product: [Fedora] Fedora Reporter: Petr Machata <pmachata>
Component: libunwindAssignee: Jan Kratochvil <jan.kratochvil>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jan.kratochvil, mnewsome
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libunwind-0.99-2.20110424git1e10c293.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-09 15:17:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Petr Machata 2011-05-09 13:55:43 UTC
Ltrace upstream uses libunwind-ptrace.a to support unwinding.  This version of ltrace is not in Fedora yet, but should get there eventually.  I can drop the unwind support for the time being, but it would be great if it were available long-term.  I know Fedora generally frowns upon shipping .a's, but this functionality is not available in any DSO to my knowledge.

Comment 1 Jan Kratochvil 2011-05-09 15:17:20 UTC
/usr/include/libunwind-ptrace.h
/* Helper routines which make it easy to use libunwind via ptrace().
   They're available only if UNW_REMOTE_ONLY is _not_ defined and they
   aren't really part of the libunwind API.  They are implemented in a
   archive library called libunwind-ptrace.a.  */

ltrace:
checking libunwind.h usability... yes
checking libunwind.h presence... yes
checking for libunwind.h... yes
checking libunwind-ptrace.h usability... yes
checking libunwind-ptrace.h presence... yes
checking for libunwind-ptrace.h... yes
checking whether to use libunwind support... yes
checking for backtrace in -lunwind... yes
checking for _UPT_create in -lunwind-ptrace... yes

checking for _Ux86_64_init_remote in -lunwind-x86_64... yes
+
checking for _Ux86_init_remote in -lunwind-x86... yes