We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When I compile LightGBM with -DUSE_TIMETAG=ON, it will show segmentation fault after my code runs. I found this caused by
LightGBM/include/LightGBM/utils/common.h
Lines 1021 to 1023 in 28536a0
The text was updated successfully, but these errors were encountered:
Thanks for using LightGBM.
Can you please share:
Sorry, something went wrong.
Thanks for using LightGBM. Can you please share: what compiler? what operating system? what version of LightGBM (or commit hash)? exact commands you used to try to build the project
Thanks for replying. Here's my version info
git clone --recursive https://github.com/microsoft/LightGBM cd LightGBM mkdir build cd build cmake -DOpenCL_LIBRARY=/usr/local/cuda/targets/x86_64-linux/lib/libOpenCL.so -DOpenCL_INCLUDE_DIR=/usr/local/cuda/targets/x86_64-linux/include -DBoost_LIBRARY=/opt/3rd/boost/lib -DBoost_INCLUDE_DIR=/opt/3rd/boost/include -DUSE_GPU=1 -DUSE_TIMETAG=ON .. && make -j cp lib_lightgbm.so python-package/lightgbm/lib/
In addition, I used std::cout instead of the original code and I found this works for me:
for (auto it = ordered.begin(); it != ordered.end(); ++it) { // Log::Info("%s costs:\t %f", it->first.c_str(), it->second * 1e-3); std::cout << it->first << " cost " << it->second / std::chrono::milliseconds(1) << std::endl; }
No branches or pull requests
When I compile LightGBM with -DUSE_TIMETAG=ON, it will show segmentation fault after my code runs.
I found this caused by
LightGBM/include/LightGBM/utils/common.h
Lines 1021 to 1023 in 28536a0
The text was updated successfully, but these errors were encountered: