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
  • #2617
Closed
Open
Issue created Aug 24, 2017 by Derek Bruening@derekbrueningContributor

xstate query signal should probably not be sent in standalone mode

In standalone mode the query signal from #1937 (closed) is still sent during initialization. This doesn't seem ideal, to have a SIGILL show up and complicate debugging, given that we disallow use of try/except when in standalone mode (presumably that includes safe reads and writes too and other uses of signals).

What about the TLS magic read? I'm not 100% sure that's avoided in standalone mode. This issue covers investigating and disabling the query signal for standalone_library.

Assignee
Assign to
Time tracking