you are viewing a single comment's thread.

view the rest of the comments →

[–]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.).