Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ESD-1836: added additional massif options #59

Merged
merged 2 commits into from
May 27, 2020

Conversation

RReichert
Copy link
Contributor

@RReichert RReichert commented May 26, 2020

Not much going on in here, except just adding some extra valgrind-massif options.

@RReichert RReichert changed the title added additional massif options ESD-1836: added additional massif options May 26, 2020
@@ -109,6 +109,18 @@
#
### MASSIF SPECIFIC OPTIONS:
#
# DEPTH maximum depth of the allocation trees recorded for detailed snapshots.
#
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you also add a unit or range to use as argument to depth?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did mention that the parameter expects a number and specified the default value. I've made this change to all the other single variable parameters as well.

There is no upper range within Valgrinds documentation (in my implementation it caps at 200), so I didn't want to specify the range as that isn't set in stone from the looks of things.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Super! 👍

#
# DETAILED_FREQUENCY frequency of detailed snapshots. With value of `1`,
# every snapshot is detailed.
#
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as above, can I use decimal numbers as argument?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✔️, marked it as float, the notation that is used in Valgrind of m.n seems a bit strange

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you prefer decimal over float I can use decimal

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I prefer float :P looks good 👍

@RReichert RReichert requested a review from Davinco May 27, 2020 03:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants