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
  • #3425
Closed
Open
Issue created Mar 07, 2019 by Derek Bruening@derekbrueningContributor

CRASH app calling ppoll with NULL sigmask

This is a bug in 69ea4ef0 for #2759. The handling of ppoll (and probably the other p* sigmask syscalls) does not gracefully handle a NULL sigmask: the code just crashes. NULL is a valid parameter:

   If the sigmask argument is specified as NULL, then no signal mask
   manipulation is performed (and thus ppoll() differs from poll() only
   in the precision of the timeout argument).

Even if it were not, DR should gracefully handle invalid parameters and should not crash on any app behavior.

Assignee
Assign to
Time tracking