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
  • #2224
Closed
Open
Issue created Feb 26, 2017 by Derek Bruening@derekbrueningContributor

client.file_io failing on win10: dr_safe_write() not returning partial size written due to NtWriteVirtualMemory behavior change

The client.file_io test is failing on win10:

116: ERROR in overlap dr_safe_write() 0x254c0000 0x254c2000 -1

NtWriteVirtualMemory is correctly writing the expected partial up to the page boundary, and returning STATUS_PARTIAL_COPY as expected.

But in ReturnLength it's returning -1! Must be a kernel behavior change as pre-win10 kernels returned the actual partial number of bytes written.

Assignee
Assign to
Time tracking