Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
aports
aports
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 639
    • Issues 639
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 193
    • Merge Requests 193
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • alpine
  • aportsaports
  • Issues
  • #565

Closed
Open
Opened Apr 04, 2011 by Matt Smith@mattx86

uclibc backtrace / libexecinfo

Seems that uclibc has had the equivalent of libexecinfo (known as libubacktrace) for some time:
http://lists.uclibc.org/pipermail/uclibc-cvs/2010-September/028267.html

If you guys think it’s useful, the uclibc option appears to be UCLIBC_HAS_BACKTRACE.

If we do switch this on, we should at least:

- remove testing/libexecinfo from aports

  • examine testing/apache-mod-backtrace

(from redmine: issue id 565, created on 2011-04-04, closed on 2011-04-30)

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Alpine 2.2.0
Milestone
Alpine 2.2.0 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: alpine/aports#565