Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • linux
  • Repository
  • linux
  • arch
  • tile
  • kernel
  • stack.c
Find file BlameHistoryPermalink
  • Chris Metcalf's avatar
    arch/tile: prevent corrupt top frame from causing backtracer runaway · dabe98c9
    Chris Metcalf authored Oct 14, 2010
    
    
    The backtracer will normally cut itself off after 100 frames anyway,
    but it's messy.  With this change we notice that the frame being
    reported is the same as the last one, and cut off the dump with a
    message similar to what gdb displays in the same circumstance.
    
    Signed-off-by: default avatarChris Metcalf <cmetcalf@tilera.com>
    dabe98c9
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7