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

Segfaults #15

Open
skinnerr opened this issue Jan 26, 2015 · 1 comment
Open

Segfaults #15

skinnerr opened this issue Jan 26, 2015 · 1 comment

Comments

@skinnerr
Copy link
Contributor

I've been working with block-cyclic ordering, and I think I have it implemented correctly now. Everything compiles fine, but when I run the program (in serial, and regardless of block size) I encounter a segmentation fault in main(), some time after all the initial print statements. I'm pretty sure it happens during the actual benchmarking. Any ideas on how to determine the cause of the problem?

@jedbrown
Copy link
Member

Valgrind is excellent. You can also run in a debugger, in which case it will trap on invalid memory access. Remember to compile with debugging symbols (-g).

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

No branches or pull requests

2 participants