nvim-gdb VS cpplinks

It's not ideal to me yet. I've had some problems with DAP. The DAP servers I've checked were a bit unstable and slow. For now I'm using gdb with nvim-gdb https://github.com/sakhnik/nvim-gdb

Very reliable and as fast as gdb is. But with all the problems just using gdb has.

Maybe https://github.com/sakhnik/nvim-gdb (bashdb uses gdb like commands) I've mostly used llvm debugger and node debugger so I am not too familiar with gdb.

nvim-gdb: GDB wrapper, simple and easy to hack.

Recently I am using nvim-gdb, which is inspired by neovim-gdb.vim script. I am wondering whether it is possible to have the same visual interface in terms of current line running as well as the breakpoint mark similar to the above two project but not connect to the debug?

There's the plugin that evolved from the original neovim debugger: sakhnik/nvim-gdb. Well tested and maintained. Spoiler: personal affiliation.

sakhnik/nvim-gdb This one also looks like a nice debugger plugin; also neovim only.

https://www.dannyadam.com/blog/2019/05/debugging-in-vim/ describes it well. https://github.com/sakhnik/nvim-gdb is nicer, but requires neovim.

More on compiler correctness in general: https://github.com/MattPD/cpplinks/blob/master/compilers.cor... and fuzzing in particular: https://github.com/MattPD/cpplinks/blob/master/compilers.cor...

Right, metamorphic testing in particular (which would be a special case of PBT, with metamorphic relations being properties), https://en.wikipedia.org/wiki/Metamorphic_testing, https://github.com/MattPD/cpplinks/blob/master/testing.md#pr...

One simple example (from the above) is "sin (π − x) = sin x" for the implementation of the sine function not requiring the knowledge of the output values. Naturally, instead of literal equality "=" one can use a more appropriate accuracy specification as a, say, relative ulp (https://en.wikipedia.org/wiki/Unit_in_the_last_place) error bound, cf. https://members.loria.fr/PZimmermann/papers/accuracy.pdf

linking and loading: https://github.com/MattPD/cpplinks/blob/master/executables.linking_loading.md - in addition to the aforementioned books and blog posts, there also some pretty good talks: https://github.com/MattPD/cpplinks/blob/master/executables.linking_loading.md#talks

For more compilers correctness* resources see https://github.com/MattPD/cpplinks/blob/master/compilers.correctness.md

As for linkers and loaders, see https://github.com/MattPD/cpplinks/blob/master/executables.linking_loading.md

More: https://github.com/MattPD/cpplinks/blob/master/atomics.lockfree.memory_model.md

Take the red pill and see how deep the rabbit hole goes... https://github.com/MattPD/cpplinks/ https://github.com/shafik/cpp_learning

x86-64 tutorials here should be a good starting point: https://github.com/MattPD/cpplinks/blob/master/assembly.x86.md#tutorials

See also static analysis resources (more C++-oriented, although some of the readings are general): https://github.com/MattPD/cpplinks/blob/master/analysis.static.md#readings-books and https://gist.github.com/MattPD/71b63a3e1600c2b52e1db80fa2834e60#correctness-in-practice (formal methods and program analysis in industry).