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

Valgrind #726

Closed
stevenrbrandt opened this issue Feb 25, 2013 · 5 comments
Closed

Valgrind #726

stevenrbrandt opened this issue Feb 25, 2013 · 5 comments

Comments

@stevenrbrandt
Copy link
Member

It would be nice if HPX applications could be checked/debugged with valgrind. Can this be made to work?

@hkaiser
Copy link
Member

hkaiser commented Feb 25, 2013

It should be possible, however I'd definitely need help with this.

@sithhell
Copy link
Member

Just checked with examples.quickstart.hello_world valgrind seems to run but reporting many errors. Hopefully those are false positives.

@hkaiser
Copy link
Member

hkaiser commented Sep 30, 2013

That's exactly what this ticket was about. Steve asked whether we could get rid of those error messages as they make it impossible to find genuine problems.

sithhell added a commit that referenced this issue Oct 1, 2013
Adding basic valgrind support
@sithhell sithhell modified the milestones: 1.0.0, 0.9.8 Mar 17, 2014
@hkaiser hkaiser modified the milestones: 1.0.0, 1.1.0 Apr 23, 2017
@diehlpk
Copy link
Member

diehlpk commented Jul 27, 2017

I had a look and most of the errors are related to boost and they mention on their website that this is a known issue and you need compile boost with valgrind=on option.

Running programs that switch stacks under valgrind causes problems. Property (b2 command-line) valgrind=on let valgrind treat the memory regions as stack space which suppresses the errors. Users must define BOOST_USE_VALGRIND before including any Boost.Context headers when linking against Boost binaries compiled with valgrind=on.

@msimberg msimberg removed this from the 1.1.0 milestone Dec 5, 2017
@hkaiser
Copy link
Member

hkaiser commented Dec 31, 2017

I think this can be closed as it has been shown to work. Feel free to reopen if needed.

@hkaiser hkaiser closed this as completed Dec 31, 2017
@hkaiser hkaiser added this to the 1.1.0 milestone Dec 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants