| Summary: | libunwind dependency is unnecessary | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Peter Hutterer <peter.hutterer> |
| Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> |
| Status: | RESOLVED WONTFIX | QA Contact: | Xorg Project Team <xorg-team> |
| Severity: | normal | ||
| Priority: | medium | CC: | jan.kratochvil, peter.hutterer |
| Version: | git | ||
| Hardware: | Other | ||
| OS: | All | ||
| URL: | https://bugzilla.redhat.com/show_bug.cgi?id=1018549 | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
Discussion from upstream ended with: "That is without fork()+exec() libunwind is currently the best there is for xserver." http://lists.x.org/archives/xorg-devel/2013-October/038475.html |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Copying from Red Hat bug 1018549: "I have found Fedora xorg-x11-server depends on libunwind. There is a longterm plan to obsolete libunwind from Fedora by new elfutils unwinder. But xorg-x11-server does not even need any external (non-glibc) unwinder. According to http://pkgs.fedoraproject.org/cgit/xorg-x11-server.git/tree/0001-os-use-libunwind-to-generate-backtraces.patch you do only self-backtrace (called local unwinding by libunwind). glibc backtrace() can do the same. According to the sample backtrace in the patch above the backtrace addresses there are the same in before/after cases, libunwind only adds resolving of address -> symbol name there, IIUC. address -> symbol name resolving can be done with RH-supported elfutils package."