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

interrupt error #7

Open
donglimf opened this issue Jan 16, 2020 · 7 comments
Open

interrupt error #7

donglimf opened this issue Jan 16, 2020 · 7 comments

Comments

@donglimf
Copy link

When I run function "depth2cloud_cuda",it will interrupt in file"icp.cu " line 274.

@meiqua
Copy link
Owner

meiqua commented Jan 16, 2020

interrupt error means segmentation fault or what? Maybe you can insert "gpuErrchk(cudaPeekAtLastError());" before line 274 to see more error messages.

@meiqua
Copy link
Owner

meiqua commented Jan 16, 2020

By the way, Does the depth image seem normal if comments back the test.cpp line 64-67?

@donglimf
Copy link
Author

1、I insert "cudaDeviceSynchronize();" and "cudaGetLastError();" befor line 270,it return 77,maybe depth2mask is error,Let me have check.
2、Depth image look normal.

Thanks for you review.

@meiqua
Copy link
Owner

meiqua commented Jan 17, 2020

depth2mask seems too simple to be wrong. Will this happen if you insert codes before depth2mask?

@donglimf
Copy link
Author

donglimf commented Jan 19, 2020

I have solve the problem,in function " render_cuda_keep_in_gpu ",if I copy depth_cuda from device to host in Function of the internal(renderer.cu),it works,but if I copy depth_cuda from device to host in test.cpp,it doesn't work.So I copy the thrust data into a device pointer,and return it.Test.cpp now works well,but I don't know why does this happen?

@meiqua
Copy link
Owner

meiqua commented Jan 19, 2020

Any function related to gpu should be in .cu file. If you want depth on cpu side, just use render_cuda.

@donglimf
Copy link
Author

It is no need to do that,cudaMemcpy can work in .cpp file. But kernel function should be in .cu file.

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