Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • G go
  • 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
  • go
  • Repository
  • go
  • src
  • runtime
  • stack.go
Find file BlameHistoryPermalink
  • Keith Randall's avatar
    runtime: identify special functions by flag instead of address · 9d421531
    Keith Randall authored Mar 14, 2018
    When there are plugins, there may not be a unique copy of runtime
    functions like goexit, mcall, etc.  So identifying them by entry
    address is problematic.  Instead, keep track of each special function
    using a field in the symbol table.  That way, multiple copies of
    the same runtime function will be treated identically.
    
    Fixes #24351
    Fixes #23133
    
    Change-Id: Iea3232df8a6af68509769d9ca618f530cc0f84fd
    Reviewed-on: https://go-review.googlesource.com/100739
    
    
    Run-TryBot: Keith Randall <khr@golang.org>
    TryBot-Result: Gobot Gobot <gobot@golang.org>
    Reviewed-by: default avatarIan Lance Taylor <iant@golang.org>
    9d421531
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7