Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D dynamorio
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,467
    • Issues 1,467
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 44
    • Merge requests 44
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • 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
  • DynamoRIO
  • dynamorio
  • Issues
  • #3023
Closed
Open
Issue created May 23, 2018 by Derek Bruening@derekbrueningContributor

HANG attaching to app that continually creates threads

A 3rd-party app that continually creates threads (similar to api.detach_spawn and other tests of ours, which are indeed flaky) can hang during static-DR attach: it hits the loop added for #2603 (closed) waiting on uninit_thread_count.

One solution is a full #1305 barrier where no threads make progress until all are attached, but I am worried about performance there for apps with many threads. Instead I'm putting in a new-thread barrier where no new threads in taken-over threads are allowed until attach is finished.

Assignee
Assign to
Time tracking