[YARP_OS] add hooks for checking heap allocation in regression tests #365
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lornat75
added a commit
that referenced
this pull request
Jan 20, 2015
[YARP_OS] add hooks for checking heap allocation in regression tests
|
@paulfitz what about malloc/free allocation? There are a few around YARP_OS, it might be worth checking for these as well... |
|
@drdanz I did look at catching malloc/free but the easy-to-do method was deprecated and the blessed method was more awkward than I wanted to get into. However maybe I missed something. It seemed easier to remove any malloc/frees in the code I'll be testing (I don't think there are any in those parts but will check) |
|
@paulfitz Have you seen this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is some support for memory checks I'll be adding in later PRs, basically adding tests that yarp does not allocate memory during performance-sensitive operations.
It relies on overriding new/delete. This appears to conflict with something ACE is doing. Reserving these tests for a no-ace build is fine for my purposes. None of this code will be run unless YARP is compiled with a special
YARP_TEST_HEAPflag (marked as advanced).