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
  • #3113
Closed
Open
Issue created Jul 30, 2018 by Derek Bruening@derekbrueningContributor

[drcachesim] do not dump trace buffer on non-blocking syscalls

Today drcachesim's tracer dumps its per-thread buffers prior to each syscall just in case it blocks, to ensure we get timely output and timestamps for thread interleaving at key thread switch points. However, this can result in too many thread interleavings and very short buffer dumps. We could have a list of syscall numbers that never block and avoid dumping prior to those if we do not want to get into the more complex game of figuring out whether a syscall will block or not (esp without history after attaching).

Assignee
Assign to
Time tracking