GDB Debugging: How to Debug a C/C++ program
Vložit
- čas přidán 22. 07. 2024
- What is the GNU GDB debugger?
This video explains what is the GDB debugger and how to debug a C / C++ program inside the Linux terminal.
A debugger is a program that allows you to pause and resume the execution of your code and makes it easier for programmers to find bugs in their code.
We will execute the GDB tool step by step to explain the most popular commands to add breakpoints, watch variables, and pause/resume the execution of C and C++ code.
GDB is a powerful debugger that allows us to work with C and C++ code from inside the operating system terminal. Mastering GDB will help you evolve as a programmer and open doors to optimize your code and find potential errors.
We will work with a very basic C sample code, where one of the functions is returning the wrong value as a result. With GDB we can break the execution, watch the value of the variables, and continue to inspect our code line by line.
For complete and comprehensive courses, including ones on the Linux operating system and other C and C++ development tools, visit:
pikuma.com
SUBSCRIBE to learn more about computer science topics:
/ @pikuma
Follow me on Twitter:
/ pikumalondon - Jak na to + styl
Still best GBD tutorial to date. 10/21
true
You are indeed a great tutor! Thanks for coming up with this in the most precise way possible
Wonderful! Loved the simplicity
never used gdb but would like to get into it
this was a perfect introduction
many thanks for sharing your knowledge
Great tutorial, thank you for this!
great tutorial. Thank you so much man
Great help. Thanks!
Thank you very much! This is really helpful!!
Thank you so much Gustavo!
I want more free videos on Linux and Game development.
I watched all your CZcams videos.
And I also enrolled for your Fundamentals of game development. And I am learning and enjoying it.
Thanks for all of your great tutorials.
And I want a SDL c++ course that teaches in-depth knowledge of game development like memory management, handling pointers, physics engine, optimization and many more cool stuff that the c++ made for.
Again thank you very much 😊
Thank you so much. I'm recordng new videos and courses as we speak. OpenGL and Game physics are the next ones. :)
@@pikuma You are my greatest teacher. That is what i wanted. I am rely excited for the new course.
If I make any game I will definitely going to add your name.
And If I will make some money I am going to support you.
Thanks you very much. I will waiting for your next course on Game Development.
I finished your Fundamental of 2D game engine.
Wow! That is my best course in my life. I learned a lot that I can't learn from CZcams videos. You shown me the power of Linux, C++ from terminal, vim the best code editor which taught me how to write code without mouse and most important fundamentals of 2D game Engine.
Now I am going to make a level editor from C++ SDL.
And I am also going to take Raycasting but I don't want to learn other languages like JavaScript.
Why don't you use c++ and lua.
Sorry for bad English.
@@AshishKumar-tg6zh This is incredibly inspiring. Thank you so much for the support. :)
Wow this is the best video i got, i always love the classic retro way of doing stuffs. Where can i find all the debugging keyboard cmd for GDB along with good explanation of same.
Fantastic.
Great tutorial! I would love to see a more in-depth debugging tutorial, though. For example, what would you do if there was a segmentation fault? Learning to debug C++ on Linux is frustrating when you are so used to Visual Studio.
True. I do believe Visual Studio is the best C++ IDE out there. Such a great piece of software...
Thank you its very help me
Valeu, Gustavo!!
Grande! 😉
Show them core file debugging and conditional watches. Also, executables should always be compiled with -g -gcc-record-switches -g3, which will make the executable significantly larger but doesn't impact execution speed since the runtime linker knows to ignore the debugging slots of the ELF file. For 0.2 ms longer that it takes to start, it's worth having the source code and the symbols embedded in the executable in case a core dump happens and debugging is required, but the source code and symbol information isn't available separately. And yes there is a practice on GNU/Linux to separate the debugging information out of such generated executable, but it relies on GNU objdump utility which isn't guaranteed to be present on other UNIX operating systems, and usually requires figuring out which additional package contains the said debugging information, so it is by no means a good practice. Therefore it is better to have the source code and the debugging information embedded in the executable. Always.
Anyway you could cover gdb for large projects? Eg: How would you go about using it with something like a game with hundreds or thousands of source files. How to easily set a break point somewhere in middle of all that to find the part of the program you need to actually step through without having to go through thousands of lines first?
Big Man !
Do you prefer to debug large code the same way ?
How I can catch an errors inside a code by third party software?
My main idea is to create game engine and catch errors of the editor and runtime code errors using GDB..
hello good presentation of gdb but from my side "layout next" is not recognized as a command...
I'm on windows system and using native "gdb.exe" program provided with my MinGW/bin repertory.
maybe you can use it from within mingw instead?
Ótima explicação. Vi que é brasileiro. Massa. Vou adquirir o curso de LUA em breve e ver se melhoro meus códigos em C. Tem previsão de migrar seus outros cursos pra Udemy? Grande abraço.
Grande Julio. Os cursos novos vão ser publicados no meu site pikuma.com. Na Udemy só vou manter os que já fpram publicados lá. Abração!
good
While I do appreciate the lesson on debugging with GDB, I saw the flaw in logic immediately without the need to use a debugger in this case.
Ha! True.
But one day you'll have a SegFault and then it will all make sense. 🙂
Or you can just use a proper IDE as well, even better.
@@pikuma It already makes sense as I currently do have code that SegFaults. Now to apply the methods you've demonstrated...
When I use "layout next" I get my code but in assembly language. I not sure why this is.
Did you use -g to compile and keep the symbols? I think I mentioned that in the video.
@@pikuma I was indeed using the g flag but it still gave me asm. I found out that I had to type "layout src" to have my c code appear
How you install gdb on the Mac with the M1 chip
Apple uses lldb instead of gdb. They are very similar.
How you make the vim editor so colourful 😅😅
Hi Pritam. It's a simple theme called Monokai. :)
👍🏾👍🏾👍🏾
Estou fazendo o curso de raycasting javascript. Muito bom depois quero fazer os demais. Voce e brasileiro?
Opa Heitor, sim! Sou do RS mas moro em Londres há uns bons anos. De onde tu é?
@@pikuma legal! Sou de são paulo. Nao tenho um ingles muito bom mas estou conseguindo entender as aulas. Voce tem cursos em portugues relacionado a programacao de jogos?
@@torto20 O pessoal me diz que as legendas automáticas mais atrapalham do que ajudam. Eu vou gerar legendas manualmente em Pt-BR em todos os cursos em alguns meses.
@@pikuma legal!!
1:03 you have a variable C E L E R Y
😅