Hi Nick, your current series regarding debugging is brilliant. I enjoyed mostly sanitizer, which probably outperforms a bit Valgrind. I am probably bad and obsolete but frankly speaking the best way (for me) for debugging purposes is ordinary printing on the terminal (for small and big projects, and frameworks). Again, exceptional YT and outstanding content. You are awesome. Thank you! Have a nice day!
Thank you! Print-based debugging can work fine in many circumstances. The main advantages of many debuggers is that they help automatically find problems without manual instrumentation (e.g., valgrind and sanitizers), or give you a way to get the same information from manual instrumentation but w/o having to modify/recompile your code. As per -usual, many different ways to do the same job. Just depends on what works best of the specific situation/you. Cheers, --Nick
Thank you for your videos with c++ and gdb, personally it is hard for me to find channel that teach c++ using linux (or maybe I am bad at searching for this kind of stuff) and found this one is really helpful because I too use linux (linux mint) I am switching from windows last year. So thank you, Sir!
*print* being a command and not a function, it doesn't take parentheses. Nice, TIL about the *commands* and how to use conditional breakpoints. thanks.
Great video. I am running in a problem can you help me? I am using clang to compile my project to lib and dll with debug symbol. I have an exe to load the lib, how can I debug the lib or dll given the exe and all the source code of dll or lib?
