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

Segmentation fault #84

Open
AndrewBoWen666 opened this issue Feb 1, 2019 · 8 comments
Open

Segmentation fault #84

AndrewBoWen666 opened this issue Feb 1, 2019 · 8 comments

Comments

@AndrewBoWen666
Copy link

OS: Ubuntu 18.04

When I run test_opencl, it showed the "segmentation fault". Any idea?

segmentation fault

@jjd06
Copy link
Contributor

jjd06 commented Feb 1, 2019

Not without a bit more information! Have you tried debugging?

@AndrewBoWen666
Copy link
Author

Sorry I forgot to attach error messages. The following messages was obtained when i use "dmesg".
error message

And here is an exception when I trying to display my devices in "step_world_v3_opencl".
error message 2
This issue is quite wired since it seems the exception indicates that I don't have any device, but as you see I do have a device when I run test_opencl. (I am not sure is this excpetion means I don't have device.)

@adityarajagopal
Copy link

With regards to the exception you are getting when you are running step_world_v3_lambda, it's saying that your vector size is 1 (suggesting it has the 1 platform that has been found), but you're accessing out of range (as it displays "Choosing platform 1"). So this exception should be fixed if you choose platform 0 instead of 1.

@AndrewBoWen666
Copy link
Author

Ahhhh... Thanks a lot. I didn't even notice the platform index, but the segmentation fault comes again as test_opencl. Do you have any idea on this?
error message 3.

@tnugent97
Copy link

Could you attach the output of your program when run on gdb? (in gdb, type backtrace after the program is run to get a breakdown of where exactly the seg fault occurs)

@JinYeeNg
Copy link

JinYeeNg commented Feb 6, 2019

segmentation_fault

For bin/test_opencl, this is the message showed when I use gdb to debug it. Let me know if the information in the image is not enough.

@tnugent97
Copy link

tnugent97 commented Feb 6, 2019

Can you change the makefile to add the flag -g? This adds debug symbols so gdb can tell us where the seg fault occurs.
Do you definitely have the correct version of openCL installed?
If you get really stuck with openCL on your machine, I would recommend using AWS. It's super easy to use!

Edit: I've also done a search for your GPU (https://www.geforce.com/hardware/notebook-gpus/geforce-gt-625m/specifications) and this seems to say only OpenCL 1.1 is supported. Not sure if this is an issue.

@JinYeeNg
Copy link

JinYeeNg commented Feb 6, 2019

Ok, thank you. My GPU which supports only OpenCL 1.1 seems to be the source of my issue.

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

5 participants