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

Segfault when not enough memory available #4

Open
programagor opened this issue May 31, 2018 · 1 comment
Open

Segfault when not enough memory available #4

programagor opened this issue May 31, 2018 · 1 comment
Labels

Comments

@programagor
Copy link
Owner

Probably some malloc() fails and return isn't checked against NULL. The segfault occurs after workers are started.

  - 6. worker   ... done.
All workers up and running
Segmentation fault (core dumped)
@programagor programagor added the bug label Jun 1, 2018
@programagor
Copy link
Owner Author

programagor commented Jun 1, 2018

The segfault occurs here:

buff[x][y]=0;

It usually occurs when x is near the end of its limit but not the very end (so no off-by-one error here), but y can be in the middle.

Repository owner deleted a comment Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant