|
@Jonathan_Blow | |||||
|
Do I dare ask what is the most reasonable way to debug a C++ program on Linux in 2020?
|
||||||
|
||||||
|
George Nakos
@_ggn_
|
1. velj |
|
very reluctantly mentioning codeclap (codeclap.handmade.network), assuming it runs on your config
|
||
|
|
||
|
Jonathan Blow
@Jonathan_Blow
|
1. velj |
|
Doesn't seem usable ... it terminates the program during dynamic loading before it even gets to main, and this is after I figured out it just doesn't understand ~ in filenames and I had to type paths out from root.
|
||
|
|
||
|
Arthur Brainville
@Ybalrid
|
1. velj |
|
gdb itself is a great debugger.
For a less "spartan" setup, look at QtCreator. It looks and feels like Visual Studio in term of debugging experience.
I have heard good things about using VsCode with the right extensions. I don't really like the UX of it and the json config. YMMV
|
||
|
|
||
|
Jonathan Blow
@Jonathan_Blow
|
1. velj |
|
gdb is basically the same program I was using to debug in 1989. It is not a great debugger.
|
||
|
|
||
|
ninepoints
@m_ninepoints
|
2. velj |
|
I spend dozens of hours debugging C++ on linux every week. The best visual debugger is VSCode (which integrates with either GDB or LLDB). Super easy to set up, at least as good as the VS debugger. Personally, I'm partial to gdb or lldb's TUI mode (GUI in terminal)
|
||
|
|
||
|
Jonathan Blow
@Jonathan_Blow
|
2. velj |
|
So far VSCode's UI seems strictly more annoying than Visual Studio's, but I will try some more and see what happens.
|
||
|
|
||
|
Matija Dizdar
@MD_notadoctor
|
1. velj |
|
printf
|
||
|
|
||
|
Joshua Noble
@shocknoble
|
2. velj |
|
This is os-agnostic
|
||
|
|
||
|
Fabien Sanglard
@fabynou
|
1. velj |
|
CLion has a great interface to gdb. Everything is done in GUI. I use it on all platform I develop on (win, macos, Linux). I highly recommend it.
|
||
|
|
||