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
  • #3538
Closed
Open
Issue created Apr 12, 2019 by Administrator@rootContributor

api.static_maps_mixup_novars is flaky

Created by: Carrotman42

static_maps_mixup_novars and static_maps_mixup_yesvars are tests which verify that setting linker vars for static+linux binaries has the expected effects from an end-to-end perspective (including the linker correctly passing along expected values). Both tests run the same code to mix up their /proc/self/maps and then run a static attach+detach, with the only difference being that the 'yesvars' version supplies the linker variables and is expected to pass whereas the 'novars' version is expected to fail for one reason or another due to the mixed up maps file.

On some platforms (e.g. CDash) it appears that the 'novars' can pass in some cases anyway. Perhaps I can try harder in mixing up the maps files.

Assignee
Assign to
Time tracking