Aborted (core dumped) when running GUI（ubuntu20.04运行basalt时系统崩掉）解决方法为下划线的红字

参考于：Aborted (core dumped) when running GUI (#57) · Issues · Vladyslav Usenko / basalt · GitLab

Nikolaus Demmel  @NikolausDemmel · 9 months ago

Maintainer

It should not happen. You'll have to provide a bit more information if you want more specific help. Does it crash for datasets mentioned in the readme?

I also suggest you try running with the debugger to see where the segfault comes from.

Nick Juarez  @nickjrz · 9 months ago

Author

Yes, it crashes for both datasets provided in the readme as well as for both installations methods. The GUI comes up and only shows a black screen. This is what the terminal shows

• Nikolaus Demmel  @NikolausDemmel · 9 months ago

  Maintainer

  Which OS version and compiler are you using?

• 正在上传…重新上传取消

  Nick Juarez  @nickjrz · 9 months ago

  Author

  I am using Ubuntu 20.04 and g++-10 gcc-10 for the compiler.

  Edited by  Nick Juarez  9 months ago

• 正在上传…重新上传取消

  Nikolaus Demmel  @NikolausDemmel · 9 months ago

  Maintainer

  Thanks, I can indeed reproduce crashes with GCC-10. Still investigating. Interestingly, for me it works fine when compiled with clang-12.

• 正在上传…重新上传取消

  Nick Juarez  @nickjrz · 9 months ago

  Author

  I was using clang-11 as specified in the development setup readme. I can try using clang-12

• 正在上传…重新上传取消

  Nikolaus Demmel  @NikolausDemmel · 9 months ago

  Maintainer

  Clang-11 also leads to crashes? Thanks, I'll have a look.

  PS: No need to try clang-13. That has known compilation issues b/c of introduced warnings etc. and is still being fixed.

• 正在上传…重新上传取消

  Nick Juarez  @nickjrz · 9 months ago

  Author

  correct! so actually basalt_mapper_sim --cam-calib /usr/etc/basalt/euroc_ds_calib.json --marg-data sim_marg_data --show-gui 1 and opt flow work fine but the other VIO tools do not which is strange.

  Edited by  Nick Juarez  9 months ago

• 正在上传…重新上传取消

  Nick Juarez  @nickjrz · 9 months ago

  Author

  do any of the tools use GPU or cuda libraries? as I found that my GPU hangs by looking at dmesg and seeing 'basalt_vio_sim[17400] context reset due to GPU hang' when trying to run the VIO.

  Edited by  Nick Juarez  9 months ago

• 正在上传…重新上传取消

  Nikolaus Demmel  @NikolausDemmel · 9 months ago

  Maintainer

  do any of the tools use GPU or cuda libraries?

  Basalt itself doesn't use GPU or Cuda directly, but for the visualization we use Pangolin which relies on OpenGL for 3D rendering.

  Btw, I think I might be seeing a different issue from you. I get some failed numeric checks, but they disappear if I disable the GUI or also when I run in Debug mode. Maybe it's a timing / threading issue. Also, I get a triggered assertion, not a segfault like you seem to get.

• 正在上传…重新上传取消

  Nick Juarez  @nickjrz · 9 months ago

  Author

  So the issue was related to my computer and the kernel version causing a GPU hang, changing the grub config to nomodeset fixed the issue for me.

  I appreciate the help on this!!