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

the exit() problem when using cpp_neighbors.batch_query() function #229

Open
cppcute-pm opened this issue Aug 24, 2023 · 2 comments
Open

Comments

@cppcute-pm
Copy link

Hello, HuguesTHOMAS!
When I try to use the function cpp_neighbors.batch_query() function in some other scenes, I find a failure case that when the code goes into this function, the code will cause exit() without any warning information or error message (I don't know whether should I use other IDE to Debug the code in C++ instead of Pycharm). This situation will happens after several loops (In every loop I will call this function once),I checked the number of points (around 60000),It wasn't the biggest number (around 150000) compared with previous loops. I also checked whether there exists nan , inf, overflow or underflow in the points data, the answer is not.
I want to know that if there exists any using limitation of this function or there are some factors that I didn't noticed.

@HuguesTHOMAS
Copy link
Owner

Hi @cppcute-pm,

The cpp functions is extremely hard to debug. The python debug mode wont work with them. You need to place cout in the cpp file to follow the code execution by printing stuff. Also you need to recompile the wrappers every time you change the cpp file. I had issues in the past and it took me quite some time to find the errors. Some ideas of possible mistakes:

  • The neighbor indices are negative or higher than the number of points
  • The batch lenghts are not correct

Good luck

@cppcute-pm
Copy link
Author

Thanks a lot for your reply!
I'll check my usecase carefully.

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