-
Notifications
You must be signed in to change notification settings - Fork 285
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
CudaImage allocate error in my project (segmentation fault) #84
Comments
I found a problem in image values, it appears that my float image have values between 0 and 1, but CudaImage expect a float image with values between 0 and 255, if I change : It is able to allocate the image, but in the download function a new error arise. The weird thing is, if I put the same code, with the same image in the main function of the launcher it works well, but in the handler that I prepared to do it, it doesn't work. In the main function prints this results:
But, if the same code is in the class which handle CudaSift it raises a segmentation fault inside of download fuction, this is the output before the error:
And this is the Disassembler:
|
Hi, i am working with this library, and I am already running the examples without problem.
My main problem is to integrate CudaSift in my project, I have add the CudaSIFT code and run well, but problem comes when I try to allocate an image in the CudaImage container where system launch a segmentation fault inside of allocate function.
I send you the code to see if there is something I am missing:
The output of my code before of the segmentation fault shows that InitCuda has initialized the graphic card correctly, the image is not empty and has the correct format (float):
Device Number: 0
Device name: NVIDIA TITAN Xp
Memory Clock Rate (MHz): 5705
Memory Bus Width (bits): 384
Peak Memory Bandwidth (GB/s): 547.7
img_32f cols: 1440; rows: 1080; channels: 1
img_32f type: 5
Disassembler (at the beginning of Allocate code, in line 5):
Thanks for the help
The text was updated successfully, but these errors were encountered: