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
  • Merge requests
  • !5796

i#5733, i#5734: Minor fixes in tests

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Abhinav Anil Sharma requested to merge i5733-max-trace-size-api-rseq into master Dec 16, 2022
  • Overview 11
  • Commits 5
  • Pipelines 0
  • Changes 5

Adds -max_trace_size to api.rseq to avoid generating too much trace data, which may cause us to run out of disk space. The issue on varying run times (and therefore trace data) is not reproducing now on the Jenkins machine, but with this change, the trace size comes down to 512K from 130M+ which is better.

Fixes an issue in the invariant checker that causes a SIGSEGV crash during error reporting when there's no shard stream available. This came up in the tool.drcacheoff.rseq test during the check_schedule_data checks that happen at the very end in print_results of the invariant checker, where we do not have the shard stream anymore. The invariant error itself is yet to be debugged (i#5734).

Issue: #5733, #5734

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: i5733-max-trace-size-api-rseq