jbehley / SuMa

Surfel-based Mapping for 3d Laser Range Data (SuMa)
MIT License
543 stars 166 forks source link

Visualization raises a segment error #26

Closed zhoupengwei closed 3 years ago

zhoupengwei commented 4 years ago

Hi! Thanks for excellent work. When I finished compiling and running the visual executable, a segment error was triggered. I checked the source code, the problem may appear new operator. The code that causes the error is std::shared_ptr fusion = std::shared_ptr(new SurfelMapping(params)); which in visualizer.cpp. the error is that zpw@msi:~/slam/suma_ws/src/SuMa/bin$ ./visualizer OpenGL Context Version 4.6 core profile GLEW initialized. OpenGL context version: 4.6 OpenGL vendor string : NVIDIA Corporation OpenGL renderer string: GeForce RTX 2060/PCIe/SSE2 段错误 (核心已转储) Do you have this error when you run the code? Can you give some solutions?

Thanks

jbehley commented 4 years ago

Can you provide the backtrace(bt) from gdb? Run gdb -ex run ./visualizerand then type bt when the program crashes.

Bur my suspicion is that it's an problem with Eigen and latest gtsam. For gtsam specific version work, please see: https://github.com/jbehley/SuMa/issues/20

zhoupengwei commented 4 years ago

@jbehley, yes,I chang the gtsam version by 4.0.0-alpha2 and eigen downgrade at 3.2.7 , now it worked well,thank you very much.

Rogers34 commented 4 years ago

@zhoupengwei hi, I use ubuntu 18.04.5, nvidia-drivers-450(GeForce GTX 1660Ti ), gtsam4.0.0-alpha2 eigen3.2.7 but i receive Segmentation fault. Could you tell me which distribution of your system? And which vesion of the lib i use is wrong.

zhoupengwei commented 4 years ago

I am using the same version in my system, You need to specify to use Eigen in the system when cmake is compiled. There are some main notices that are due to source installation of Eigen, its path will be located at /usr/local/include/. The path to install Eigen directly using the command is different, it is located at /usr/include. I just copy /usr/local/include/eigen3 to /usr/include/ after finished compiling it. The compilation command is roughly as follows: cd gtsam/ mkdir build && cd build cmake -DGTSAM_USE_SYSTEM_EIGEN=ON .. sudo make install

Hope to help you! Regards PengWei

JingYang notifications@github.com 于2020年8月19日周三 下午4:31写道:

@zhoupengwei https://github.com/zhoupengwei hi, I use ubuntu 18.04.5, nvidia-drivers-450(GeForce GTX 1660Ti ), gtsam4.0.0-alpha2 eigen3.2.7 but i receive Segmentation fault. Could you tell me which distribution of your system? And which vesion of the lib i use is wrong.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jbehley/SuMa/issues/26#issuecomment-675942499, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANKJGYVEQ37UWQETPN3KQ4DSBOEVHANCNFSM4PPVVDOQ .

Rogers34 commented 4 years ago

我的eigen是安装在usr/include下的 gtsam编译的时候也选了use_system_eigen 还有没有其他的要注意的

zhoupengwei commented 4 years ago

没有了, 这个错误是由于Eigen3.3系列的版本引起的 换成3.2系列的就可以了, gtsam可以用最新的版本编译.

JingYang notifications@github.com 于2020年8月19日周三 下午8:50写道:

我的eigen是安装在usr/include下的 gtsam编译的时候也选了use_system_eigen 还有没有其他的要注意的

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jbehley/SuMa/issues/26#issuecomment-676300937, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANKJGYR22W2CJOEBKIY5MMTSBPDBBANCNFSM4PPVVDOQ .

Rogers34 commented 4 years ago

我尝试了很多组合,最后gtsam4.0.3+eigen3.2.10 能运行

jbehley commented 3 years ago

Is the problem resolved?

zhoupengwei commented 3 years ago

Yes, this problem has been solved, thank you very much!

Jens Behley notifications@github.com 于2020年12月30日周三 上午7:00写道:

Is the problem resolved?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jbehley/SuMa/issues/26#issuecomment-752269617, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANKJGYWL75Y3WNPUF3Q7A3TSXJNRRANCNFSM4PPVVDOQ .

jbehley commented 3 years ago

Good to hear! Then I close now this issue. If you could provide some comment on the actual solution for others that would be highly appreciated.