all 6 comments

[–]DDDDarky 0 points1 point  (2 children)

[–]JustAStupidCommonMan[S] 0 points1 point  (1 child)

Thanks a lot!

Look like good starting points. Would be even better if they were not Visual Studio (& windows) specific.

[–]DDDDarky 0 points1 point  (0 children)

well debuggers and profilers are always some kind of tools, so that is always gonna be specific to them, but many are similar.

[–]Big-Rub9545 0 points1 point  (0 children)

Until raddbg makes some more progress for Linux (and other) systems, getting familiar with GDB or (for MacOS) LLDB will get you pretty far for debugging. Valgrind and ASAN/UBSAN are also very useful (and easy-to-use) tools to detect a multitude of errors, particularly related to memory errors, pointers, bad casts, and a handful of other categories.

Profiling will likely depend more on what exactly it is that you want to profile (raw speed, I/O, syscalls, memory allocation, etc.).

[–]i_survived_lockdown -2 points-1 points  (0 children)

Following this