Debugging C Programs with GDB

preview_player
Показать описание
In this video, we learn how to debug C programs with GDB.

◾◾◾◾◾◾◾◾◾◾◾◾◾◾◾◾◾
📚 Programming Books & Merch 📚

🌐 Social Media & Contact 🌐

Рекомендации по теме
Комментарии
Автор

This helps me as I’m learning C for my university degree. Much appreciated. Keep up the great work 🤗

tibish
Автор

Never have I imagined one day I'd be debugging with minimal UI like this. Thx for the vid.

thechronicler
Автор

Just finished an Operating Systems class and was talking with my brother in law about how hard it is to debug C with just printfs, and he was confused I wasn't using GDB. My teacher never taught us it existed. I'm so mad

kid-presentable
Автор

at 9:14, it is an unfortunate choice to have your file named main.c because if the file were called hello.c for example you would also use >disassemble main and not >disassemble hello because there is an inherent assumption in the way you presented it !

edwardmacnab
Автор

I have been programming in C for 40 years and the only command I know in gdb is "where", once I see the stack trace I usually know where the issue is.
The best tool for debugging C is your brain.

turdwarbler
Автор

would be cool if you could more in depth with C

lennuard_
Автор

So nice a guide. Loved it! And I like your microphone. You should have skipped the part of writing the actual code since it's not the point of the guide. It is also nice that you added that skipping ability so one can just go straight to debugging. Still some users will miss the video because of the length not knowing it is in fact organized in chapters. I'm speaking of those who need just a focused video on debugging.

michaelciyke
Автор

debugging C on your PC is one thing. The real "fun" starts when you try to debug an embedded program that you burned to an IC...

salsamancer
Автор

Thank you, very useful for neophyte :)

esimitley
Автор

cool, thank you for dedication. Do you consider making videos about Rust or Go in future?

knowledgedose
Автор

Cool, thanks, I love this video, I learned new good stuff! Actually I got to this video, because after several tries, I couldn't seem to make the VScode work properly... I know I'm a noob...

digitalrew
Автор

not a single person shows the first step, where are you opening the file or anything like that, there is no help really for gdb beginner, how to use text editor, gnu or shell together, I never heard of gdb and everyone says you use this comman and install gdb, only minigw video, explains atleast the first part

ADwaMoviesandMusicsproduction
Автор

Do we need GDB ? Visual studio code has good debugging system with breakpoints that you mentioned for Pyhton. So should we use VSCode ?

Kapkar
Автор

you might have said that in >nv main.c at the bash prompt nv is a custom alias that you've set up and that to terminate the shell running the c program you use ^c or ctrl + c and you probably should have cited all the documentation sites for gdb and to really scare people gcc, nano, and glibc . Actually I have learned that ^d or ctrl + d is the proper way to terminate

edwardmacnab
Автор

Is it possible to have gdb display all relevant variables to the current scope(or global and local) and update them with each step like vscode does? or do you have to type print for each variable every step?

smashy
Автор

What is the nv command do? Is that a text editor like vim or nano? Not familiar

johnwight
Автор

Hi! Why actually going that way if you have codeblocks or eclipse or other IDEs?

Jonathan-ruzl
Автор

6:38 My god, doesn't your console have a scrollbar?! 😂

exnihilonihilfit