Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
W wendelin.core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Levin Zimmermann
  • wendelin.core
  • Repository

Switch branch/tag
  • wendelin.core
  • t
  • tfault-run
Find file BlameHistoryPermalink
  • Kirill Smelkov's avatar
    bigfile/virtmem: Print traceback on segmentation fault · 25fa18f4
    Kirill Smelkov authored Aug 11, 2021
    Do what we can do without gdb and then tail to regular segmentation
    fault. With core file gdb can still be used, but it is handy if we
    already can get traceback of the crash into the log automatically.
    
    TODO better use https://github.com/ianlancetaylor/libbacktrace because
    backtrace_symbols often does not provide symbolic information.
    
    We do not do this now because libbacktrace is not always automatically
    installed.
    25fa18f4
tfault-run 1.24 KB
EditWeb IDE

Replace tfault-run

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7