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

DROPTION_FLAG_ACCUMULATE is not reset on detach

drcachesim has an accumulation option -record_function and you can see in the burst_malloc test, which does several re-attaches, that the option is never reset on detach:

$ ctest -V -R burst_malloc
pre-DR init
Warning: duplicated function name malloc in -record_function or -record_heap_value malloc|1&free|1&tc_malloc|1&tc_free|1&__libc_malloc|1&__libc_free|1&calloc|2&malloc|1&return_big_value|1
pre-DR start
pre-DR detach
DynamoRIO statistics:
<...>
all done
pre-DR init
Warning: duplicated function name malloc in -record_function or -record_heap_value malloc|1&free|1&tc_malloc|1&tc_free|1&__libc_malloc|1&__libc_free|1&calloc|2&malloc|1&return_big_value|1&malloc|1&return_big_value|1
Warning: duplicated function name malloc in -record_function or -record_heap_value malloc|1&free|1&tc_malloc|1&tc_free|1&__libc_malloc|1&__libc_free|1&calloc|2&malloc|1&return_big_value|1&malloc|1&return_big_value|1
Warning: duplicated function name return_big_value in -record_function or -record_heap_value malloc|1&free|1&tc_malloc|1&tc_free|1&__libc_malloc|1&__libc_free|1&calloc|2&malloc|1&return_big_value|1&malloc|1&return_big_value|1
pre-DR start
pre-DR detach
DynamoRIO statistics:
<...>
all done
pre-DR init
Warning: duplicated function name malloc in -record_function or -record_heap_value malloc|1&free|1&tc_malloc|1&tc_free|1&__libc_malloc|1&__libc_free|1&calloc|2&malloc|1&return_big_value|1&malloc|1&return_big_value|1&malloc|1&return_big_value|1
Warning: duplicated function name malloc in -record_function or -record_heap_value malloc|1&free|1&tc_malloc|1&tc_free|1&__libc_malloc|1&__libc_free|1&calloc|2&malloc|1&return_big_value|1&malloc|1&return_big_value|1&malloc|1&return_big_value|1
Warning: duplicated function name return_big_value in -record_function or -record_heap_value malloc|1&free|1&tc_malloc|1&tc_free|1&__libc_malloc|1&__libc_free|1&calloc|2&malloc|1&return_big_value|1&malloc|1&return_big_value|1&malloc|1&return_big_value|1
Warning: duplicated function name malloc in -record_function or -record_heap_value malloc|1&free|1&tc_malloc|1&tc_free|1&__libc_malloc|1&__libc_free|1&calloc|2&malloc|1&return_big_value|1&malloc|1&return_big_value|1&malloc|1&return_big_value|1
Warning: duplicated function name return_big_value in -record_function or -record_heap_value malloc|1&free|1&tc_malloc|1&tc_free|1&__libc_malloc|1&__libc_free|1&calloc|2&malloc|1&return_big_value|1&malloc|1&return_big_value|1&malloc|1&return_big_value|1
pre-DR start
pre-DR detach
DynamoRIO statistics:
<...>
all done

droption today has no control point on exit or detach. Maybe it could provide a droption_reset_values() function and clients could call it in their exit events?

Assignee
Assign to
Time tracking