Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pike pike
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 119
    • Issues 119
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pikelang
  • pikepike
  • Issues
  • #8202
Closed
Open
Created Aug 30, 2019 by Peter Bortas@zinoOwner

Stringify Thread.MutexKey in backtraces

Imported from https://youtrack.roxen.com/issue/PIKE-202

Reported by Jonas Walldén jonasw@roxen.com

The improved _sprintf() in Thread.MutexKey is not visible in backtraces since that code excludes certain objects to avoid unwanted references. It would be helpful if the stringified form of the object is substituted instead in low_backtrace() (where it currently inserts a FakeObject placeholder).

Assignee
Assign to
Time tracking