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

Bus error (SIGBUS) #31

Open
tanya-kta opened this issue Nov 14, 2020 · 5 comments · May be fixed by #58
Open

Bus error (SIGBUS) #31

tanya-kta opened this issue Nov 14, 2020 · 5 comments · May be fixed by #58
Assignees
Labels
bug Something isn't working

Comments

@tanya-kta
Copy link
Member

When running in the debug mode with compilation for GPU, SIGBUS is raised in main.cu inside main while trying to get access to simulation_map->nodes

@tanya-kta tanya-kta added the bug Something isn't working label Nov 14, 2020
@kolayne
Copy link
Member

kolayne commented Nov 15, 2020

Thanks for your report! Unfortunately, I am not able to reproduce this. I was running the version from master (e150e17) with 5 as the argument to generate_cube() and the break (main.cpp:66 and main.cu:166) commented out because I don't have a visualization running.

When running the project in the debug mode with GPU compilation, I get the cudaErrorIllegalAddress: an illegal memory access was encountered error message in my stderr, the program exits with the 188 exit code (if you try to investigate it a bit deeper, you're going to figure out, that the illegal memory access happens inside of the init_simulation_objects global function, whose only work now is to create SimulationMap, so I think the error's origin is somewhere there. However, I am not 100% sure about it, the error could also be raised because of #32. I am going to dig deeper around it later).
When running in the debug mode with CPU compilation, I get the Request failed, error: Failed to connect: Connection refused Error sending http request to visualization. Stopping the simulation process error in my stderr and the program exits with the 139 exit code (SIGSEGV). By the way, this error seems to exist during the whole project's life...

@kolayne
Copy link
Member

kolayne commented Nov 16, 2020

@tanya-kta, are you still able to reproduce the issue?

@tanya-kta
Copy link
Member Author

tanya-kta commented Nov 16, 2020

Yeah, I am still able to reproduce the issue. (May be I'm doing something wrong, but I don't think so). I runned the last for today version from master in the debug mode with GPU compilation with 5 as the argument to generate_cube() and got SIGBUS again, main.cu, 125.

@tanya-kta, are you still able to reproduce the issue?

@kolayne
Copy link
Member

kolayne commented Nov 19, 2020

@tanya-kta, I guess, I see. As far as I'm concerned, the problem, causing the error, is logical. I've opened a new issue (#38) because I am not sure its fix will also remove this issue, but I believe they are describing the same problem. Please, take a look at it

@kolayne
Copy link
Member

kolayne commented Nov 19, 2020

Please, check if you can reproduce the same issue in #40. It is not intended to fix the problem, but it might have fixed it

kolayne added a commit that referenced this issue Nov 24, 2021
…nstead of previous approach.

This might have fixed one or many of: #29, #31, #38

Co-authored-by: Nikolay Nechaev <Nikolay_Nechaev@mail.ru>
@kolayne kolayne linked a pull request Nov 24, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants