800 record? You were so underrated back then, considering that even six years later you still have the best C++ tutorial. The most precise, practical, professional, up-to-date and easy to understand. And you are so passionate in these videos too! I've had a headache trying to learn C++, because they only teach what the code means and how to set up the tools for compiling, but give no understanding of how it actually works top-down. It's so hard to grasp the process without CS education, I wasn't really learning and coding most of the time, but collecting scraps of information from different materials trying to build the image of how a process should work. But after your vids about compiler & linker I'm so fired up! I finally know what I'm doing when I write the code. I can't thank you enough!
Well, as a person who is having CS education (and still doing good), I realized that what I know is... almost nothing, compared with UA-cam academy in general and specifically in this series. Got to say that I also feel the same, and it helped me a lot, as now I really understand how things work, at least now it make sense.
Another CS fellow here, still in first sem. I wanna say that I can write code that's sufficient for problem solving but even if I get it to work without copying someone else's code there's still that question in the back of my head "but why?". Why do things this way, what it actually means. The whole reason I like coding in general is the sort of magical feel you get when you build something out of nothing (it's not the instant gratification I chase I swear ;) . But then you get stuck on these questions and it's like someone took away that magic, like everything you're doing is using someone else's power(which is both true and not true). So these c++ videos are a treasure trove that just never ends.
being able to watch the memory allocation that much close is fascinating for me, like you can actually see those value getting stored physically in that hardware is just amazing :O
wow i have a little bit of programming experience and this series has really helped me to understand the nitty gritty of the whole programming process. tysm for making this
This really is the best C++ tutorial on UA-cam, I'm running through it again for the 2nd time because Cherno just knows how to teach you how to think like a programmer, even if you're not planning to use C++.
Debugging is love, debugging is life. haha for real: I partially enjoy debugging, its like solving a puzzle.. It can get reaaally frustrating some times, and sometimes even irritating, but over all its a key part of coding and learning to code better I think :)
ΜrCookie I once was using an external library and apparently my code kept crashing. Unfortunately I didn't trace it back to the library since the debugger told me a pointer was deconstructed (the class). After a few hours of hair pulling, I found out the library was manually calling the destructor.
I always used print statements to check execution. Never thought that debugging could have be way easier than that. Thank you Cherno for teaching me how to debug.
I have no experience in programming and I have been learning c++ for 4 days. I had to watch this video 3 times to fully understand it, but it was awesome. Thank you!
For those not well versed in VS17, Ctrl+F10 (or right-click Run-To Cursor) is a better way of moving from an existing point, to another point in the code (i.e., skip through a for loop)
Ohhh my goodness. I can finally see what is going on in the background while writing code. Can’t believe I’ve been going to school for more than 2 years and nothing like this was ever mentioned.. how??? God bless you The Cherno
you should sell those pillows as merch seriously, i'm sure lots of us would happily support the channel that way especially those who don't want to do the whole patreon thing
For XCode users: - Memory View : ⌘⌥⇧M or through the Debug --> Debug Workflow --> View Memory menus. - Autos and Locals are available by clicking on the arrow at the very bottom of the debug console. - To Watch a variable: Right-click on a variable and click on "watch", or right-click on the debug console and click on "add expression"
I think the fact I did not learn how to use the debugger caused that I didn't become a programmer, I used printfs to debug my programs on uni and it was very frustrating and stopped my progress a lot. It was not the only thing - I had different ideas about myself back, a lot of personal issues, but watching this episode right now after 15 years really hits a spot. Maybe I will return to programming :)
i wish i could watch this in my first year of university so that i would not be so frustrated debuging wrongly, now i am a little left behind🩼 but still very fun and helpful to watch
If you're getting random stuff instead of the cc groups, one of the things you can do to fix it is check to make sure you're on the same solution platform (x86). Switching from x64 to x86 fixed it for me.
Yeah I couldn't see the memory it said (error reading string), then I changed from x64 to x86 and it worked, even though my computer says it has a x64 processor
@@Shah_Khan Here's a decent enough explanation I found: The absence of cc in the Memory 1 window on x64 is due to the architectural differences between x86 and x64, with the latter relying less on condition codes for control flow. You can still access condition codes in the Registers window during x64 debugging.
++i should increment before the comparison, i++ should compare then increment. Unless you are saying that i++ is the last part of the "for" statement and so i++ will increment at the end of each pass. Easy to test by printing i to the screen in the body of the loop.
@@mytech6779 I know this is a really late reply, but this is incorrect. ++i and i++ don't make a difference in the header of a for loop (I believe this is because modern compilers optimize i++ to ++i). However when assigning a variable it does make a difference. If you have a variable x and its value is 7, when you do int j = ++x; the value of j will be set to 8 because the increment operator is applied to x before assignment. However, if you do int j = x++; then the value of j will be set to 7 because the value of x is assigned to j before it gets incremented.
What's awsome is my favorite coding youtuber(you)just happens to have made a c++ tutorial series which I found as I decided to learn c++. not only is this series way more informative than any other series or video I have tried but it geared toward the one thing I wanted to learn c++ for in the first place... Game dav 😂🎉🎉🎉🎉🎉
Your timing is impeccable. Just when there's something I need to know like c++ header files or debugging in VS ( like today ) you upload a video on exactly that. Thanks!
I am studying C++ on a 1300 pages book, currently around page 850, but being a VS feature I've never used and just discovered Breakpoints and Debug mode only thanks to Cherno. Thank you!
Another neat feature in debugging is you can set a condition to only break when the condition has been met. Pretty useful inside loops where you don't want to break everytime it hits the breakpoint. I.e., # Break only when i == 5 for (int i = 0; i < 100; i++) { std::cout
Thank you. TQ. TQ. I just performed my first debugging for a program. I even ended up using the Memory Window to check the values in my array change right in front me (I was "stepping over") and see the problem. It just felt so good. Best Video Ever!
Hit like those who have been programming in Visual Studio for more than 2 Years and still checking this amazing video and learned a lot. U r da best Cherno :) Keep continue ur excellent effort (Y)
"I use the console" would have been more realistic. Anyway he is clearly highlighting some functionalities to let you know they're there if you need them
Coolest thing in c++! made me understand header files more by just playing around with it!
7 років тому+12
Quick question or maybe and idea for a future video: During debug at around 12:42 the memory view showed a perfect example of byte order, most significant, least significant bit and in general the architecture of the cpu coloured in red. Would be awseome for a future episode to talk about why it's written as "08 00 00 00" instead of "00 00 00 08". Love watching your videos, they refresh my memory a lot!
It is that bytes are saved in inverted order Your PC can only manipulate bytes (8bits) and not single bits Each byte has it's own place and name So when you wanna read a number that is bigger than a byte you will need to acces two "places" So let's assume we save F7 65 (this takes up 2 bytes, Hexadecimal is designed so that each number equals 4 bits so two make up one byte that's why they are speperated like this) in what is called FE0037 It will use FE0037 and the next one (in this case FE0038) to save the number But now what if we wanna read this in 8 bit instead of 16 bit mode (16 bit is when we use 2 byte, 8 when a single one) So let's read FE0037 (the smaller one) If it were saved in normal order we would end up with F7 which in no way equals F7 65. It equals that as much as 60 equals to 6054. Better it would be to get 65 which does have euqal the lower part of the number, just like how 54 is 6054 minus 6000. And that's why we save this 65 on the byte we accesed. It makes accessing that byte again in a different processing mode more logical instead of having to think about in what mode you were and from there count upwards to which byte you have to acces to get a somewhat logical representation.
thank you...i was a bit scared to play with memory and debugging but now i feel a bit confident. great video and thanks for codelite too. Its a nice simple ide
Hi Cherno. I just loved this series. Its a great fun. Please continue with this. Currently I will not be able to pay but definitely a lot of love n respect for what you are offering.
Just a point of note: You need to be in debug mode in order to open the memory window. It means you place a break point, start debugging and then go to the menu Debug -> Windows to see the Memory option. I couldn't find it and a simple search revealed this fact. When Cherno opened the memory window, he was already in the debug mode.
This video should be the prerequisite for introduction to programming lectures in college to understand what we are going to do . Thanks for fascinating explaining
Han Solo if you have asked me that question, I would have replied "too many." Lolol. I sell guitars in my mother's shop. I wish I could learn to play guitars, yet I have never touched any guitar in my family's shop. I just never get the time for guitar tutorials.
Han Solo I don't really own all the guitars in my family's shop. I was only joking in my last comment. I felt rich which I said "too many." I can write music only in my head and I would love to put that on paper or on musical instruments. I can play piano only just a little, but I don't get free time for myself. Besides I have other hobbies in the evenings and on lazy Sunday. Someday, I will get around to learning guitar or ukulele.
The only thing i wish these youtube tutorials would do, is provide some exercises for each video with an answer key (if one wants to look). I listen to the video, I am pretty sure i understand it but i guess i just need the confirmation that I have grasped the essence of what is being taught in each video. I am not complaining as i am in the beginner stages of learning so, what would i know?. Anyways, liked and subscribed. P.S There is something about the cool color gradients and the soft music in the background of these videos that keeps me coming back.
hey guys I am using vs2022 and I found that when I set break points inside the main function as shown in the video, it is not paused as expected, it will just continue. But my breakpoint is a solid red point which means it is a valid breakpoint.
Cherno please I need to know what's the background music starting at 6:24 Anyway love this series so much. More deep knowledge of c++ about how it works
You can also CTRL+F10 and it will run to where the current line where the cursor is. Use that all the time, makes "regular" breakpoints almost useless.
I think we are at a point where people who have no idea about programming have stopped watching. So there wouldn't be too much point in covering very basic stuff like for loops and if statements. Keep up the good work!
Adhyyan He gets to the bottom of everything. It creates a solid base to work from. You could learn something you had no idea you didn't know. It's worth the listen to me. But then again I'm still pretty new. Still here tho. I'm for real trying to learn this so I definitely appreciate the details. I get how it might get boring if you already know most of this but he did say at the beginning that he wanted to create a thorough c++ course that teaches people everything they need to know to create clean, fast code. So hey hey I'm still here don't ya dare take them details away from scrubs like me. Lol
And yet, about no one noticed he got the order of execution wrong lol... it increments before checking the condition while he says that it checks then increments.
Omg the orange guitar is actually an ideally looking electric guitar that i dream about. Edit: This video has to watch every programmer in the world by my opinion. i did not know anything about "cc". Thank you, Cherno!
Hello, I have a problem at around 10:30 when you start explaining the memory, to be precise where it shows the hexadecimal values of a, and here you got all cc values, where I got values for variable a: b5 3b 1f ...etc. Is there some setting that I may have missed?
Nvm fixed it, I had some problems with the properties of the project. I went back to "How C++ works" and just copied the settings from Cherno that he just blazed thru them and it fixed it for me. UA-cam 0.25 speed helped me with the pausing between those fast frames xD
For some reason when I hover over "message" like at 6:37 Visual Studio tells me "Error reading characters of string" o.o What's wrong? My code appears to be exactly the same as his.
This series is fantastic. I noticed that you mentioned the default value before initialization in debug mode will be 0xcc, and I just curious is that fits for all debugging tools or just Visual Studio? Since I've tried this in gdb and found the value is not 0xcc...
Hey, for start props! amazing tutorial. Quick question, I am following exactly your steps, but I do not get a bunch of cc in the memory space of my "a" variable (memory1). However when I continue the code it gets assigned the correct value. Why is that? Does that mean I do not purge the memory prior to assigning a value?
At 8:55, the arrow keeps passing "int a = 8;" when I start the debugger. I'm not sure how to check the value of "a" either. Information on what's happening would be appreciated.
You can feel that he really knows his stuff and spent years for it. I really appreciate how it is free for us to enjoy.
2:33 - Please, if you're going to quote my parents, at least mention them in the description.
Lmao
lol
That hits home
😂😂😂
@@SankoshSaha_01, you ok?
800 record? You were so underrated back then, considering that even six years later you still have the best C++ tutorial. The most precise, practical, professional, up-to-date and easy to understand.
And you are so passionate in these videos too!
I've had a headache trying to learn C++, because they only teach what the code means and how to set up the tools for compiling, but give no understanding of how it actually works top-down. It's so hard to grasp the process without CS education, I wasn't really learning and coding most of the time, but collecting scraps of information from different materials trying to build the image of how a process should work.
But after your vids about compiler & linker I'm so fired up! I finally know what I'm doing when I write the code. I can't thank you enough!
Well, as a person who is having CS education (and still doing good), I realized that what I know is... almost nothing, compared with UA-cam academy in general and specifically in this series. Got to say that I also feel the same, and it helped me a lot, as now I really understand how things work, at least now it make sense.
Another CS fellow here, still in first sem. I wanna say that I can write code that's sufficient for problem solving but even if I get it to work without copying someone else's code there's still that question in the back of my head "but why?".
Why do things this way, what it actually means. The whole reason I like coding in general is the sort of magical feel you get when you build something out of nothing (it's not the instant gratification I chase I swear ;) . But then you get stuck on these questions and it's like someone took away that magic, like everything you're doing is using someone else's power(which is both true and not true). So these c++ videos are a treasure trove that just never ends.
The most enjoying C++ series ever
instablaster...
Agree
being able to watch the memory allocation that much close is fascinating for me, like you can actually see those value getting stored physically in that hardware is just amazing :O
wow i have a little bit of programming experience and this series has really helped me to understand the nitty gritty of the whole programming process. tysm for making this
This really is the best C++ tutorial on UA-cam, I'm running through it again for the 2nd time because Cherno just knows how to teach you how to think like a programmer, even if you're not planning to use C++.
Debugging is love, debugging is life. haha
for real: I partially enjoy debugging, its like solving a puzzle.. It can get reaaally frustrating some times, and sometimes even irritating, but over all its a key part of coding and learning to code better I think :)
ΜrCookie
I once was using an external library and apparently my code kept crashing. Unfortunately I didn't trace it back to the library since the debugger told me a pointer was deconstructed (the class). After a few hours of hair pulling, I found out the library was manually calling the destructor.
I find that the satisfaction of defeating a really nasty bug is one of the best feelings when coding!
It's also the most defeating... I mean it's always so easy in hindsight. Makes you rethink your belief in your prescience
Is this C/C++?
But the real question is, do you chocolate chip?
I always used print statements to check execution. Never thought that debugging could have be way easier than that. Thank you Cherno for teaching me how to debug.
Love how you explains it first and show it after, it's like you are creating the dots so it's easier for us just to connect them
It's so great to find a series that teaches the way I learn. Thank you for the effort you put into this!
REALLY wish I had this when I started programming. This is fantastic.
Yeah that pillow looks great
Much love, Yan. This is one beautifully executed series.
Learning soo much from this series. Never knew you could view the actual memory. That is fantastic.
I have no experience in programming and I have been learning c++ for 4 days. I had to watch this video 3 times to fully understand it, but it was awesome. Thank you!
Literally the best C++ tutorial series on the internet, thank you!
For those not well versed in VS17, Ctrl+F10 (or right-click Run-To Cursor) is a better way of moving from an existing point, to another point in the code (i.e., skip through a for loop)
Ohhh my goodness. I can finally see what is going on in the background while writing code. Can’t believe I’ve been going to school for more than 2 years and nothing like this was ever mentioned.. how??? God bless you The Cherno
you should sell those pillows as merch
seriously, i'm sure lots of us would happily support the channel that way especially those who don't want to do the whole patreon thing
4:25 Well, you taught me so much in two minutes. So I can see what the variables are set to without having to use cout
For XCode users:
- Memory View : ⌘⌥⇧M or through the Debug --> Debug Workflow --> View Memory menus.
- Autos and Locals are available by clicking on the arrow at the very bottom of the debug console.
- To Watch a variable: Right-click on a variable and click on "watch", or right-click on the debug console and click on "add expression"
Could you please guide me how to debug crash program?
I think the fact I did not learn how to use the debugger caused that I didn't become a programmer, I used printfs to debug my programs on uni and it was very frustrating and stopped my progress a lot. It was not the only thing - I had different ideas about myself back, a lot of personal issues, but watching this episode right now after 15 years really hits a spot. Maybe I will return to programming :)
i wish i could watch this in my first year of university so that i would not be so frustrated debuging wrongly, now i am a little left behind🩼 but still very fun and helpful to watch
Imagine if you didn't stop, you'd have 15 years of experience, and that's like senior's grandsenior, you'd be rolling in cash 💀
The pillow is almost perfectly aligned with the couch.
Hehe, I also took notice of that
If you're getting random stuff instead of the cc groups, one of the things you can do to fix it is check to make sure you're on the same solution platform (x86). Switching from x64 to x86 fixed it for me.
Yeah I couldn't see the memory it said (error reading string), then I changed from x64 to x86 and it worked, even though my computer says it has a x64 processor
Any reason for that?
@@Shah_Khan
Here's a decent enough explanation I found: The absence of cc in the Memory 1 window on x64 is due to the architectural differences between x86 and x64, with the latter relying less on condition codes for control flow. You can still access condition codes in the Registers window during x64 debugging.
@@ginsutime2963 thanks for explaining🙂
15:30 - actually, at the end of the loop it will run i++ first, and then do the comparison to check if i < 5
++i should increment before the comparison, i++ should compare then increment. Unless you are saying that i++ is the last part of the "for" statement and so i++ will increment at the end of each pass. Easy to test by printing i to the screen in the body of the loop.
@@mytech6779 I just tested and what @Flaming Taco says is true.
@@mytech6779 I know this is a really late reply, but this is incorrect. ++i and i++ don't make a difference in the header of a for loop (I believe this is because modern compilers optimize i++ to ++i). However when assigning a variable it does make a difference. If you have a variable x and its value is 7, when you do int j = ++x; the value of j will be set to 8 because the increment operator is applied to x before assignment. However, if you do int j = x++; then the value of j will be set to 7 because the value of x is assigned to j before it gets incremented.
I have found this to be accurate. I was watching i, and it said i was 4, but it was grayed out, apparently it becomes "undefined" after the for loop.
What's awsome is my favorite coding youtuber(you)just happens to have made a c++ tutorial series which I found as I decided to learn c++. not only is this series way more informative than any other series or video I have tried but it geared toward the one thing I wanted to learn c++ for in the first place... Game dav 😂🎉🎉🎉🎉🎉
This the best video I have ever seen in the Programming context.... I Love the way you teach it
Seeing how easy Visual Studio makes breakpoints has sold me on it.
Your timing is impeccable. Just when there's something I need to know like c++ header files or debugging in VS ( like today ) you upload a video on exactly that. Thanks!
"this all about figuring out...what did i do wrong? what did i do to deserve this?"
im gonna be good at this
In my University we use Visual Studio as IDE in most of the classes and I took C, C++ and C# courses using this IDE yet I am just learning to debug
Thank you I just got into C++ a few months ago and in that i have learn a-lot from your videos using VS IDE. Keep it coming!!!
I am studying C++ on a 1300 pages book, currently around page 850, but being a VS feature I've never used and just discovered Breakpoints and Debug mode only thanks to Cherno. Thank you!
umm can you help me with VS code like i still didn't get that where is diagnostic tools and memory window in the latest VS code IDE
@@Kanak_Bodkhe I'm using VS Community, not sure if it's the same
@@MicheleSollazzo yeah I realised 2 days ago that VS and VS code are different 🥲
I will definitely be buying some of your merch when I get my first job as a developer. You are a great teacher.
if you can"t debug where you want just change setting of optimization(project properties->C/C++ ->Optimization-> Disable)
I really appreciate your comment, I was looking for this the last two hours. Thank you so much!
Another neat feature in debugging is you can set a condition to only break when the condition has been met. Pretty useful inside loops where you don't want to break everytime it hits the breakpoint.
I.e.,
# Break only when i == 5
for (int i = 0; i < 100; i++)
{
std::cout
Thank you. TQ. TQ. I just performed my first debugging for a program. I even ended up using the Memory Window to check the values in my array change right in front me (I was "stepping over") and see the problem. It just felt so good. Best Video Ever!
The most entertaining C++ series to date and do you have lessons about flutter mobile?
Hit like those who have been programming in Visual Studio for more than 2 Years and still checking this amazing video and learned a lot. U r da best Cherno :) Keep continue ur excellent effort (Y)
Cherno: "If you are programming without this - I do not know what you are doing?" (@4:21)
Me: "Everything perfectly! :) :) :)"
"I use the console" would have been more realistic. Anyway he is clearly highlighting some functionalities to let you know they're there if you need them
I never saw a tutorial with so deep details, so you really understand whats going on inside mashine - thank you !!
The best c++ series I found on youtube. Really inspiring
Coolest thing in c++! made me understand header files more by just playing around with it!
Quick question or maybe and idea for a future video: During debug at around 12:42 the memory view showed a perfect example of byte order, most significant, least significant bit and in general the architecture of the cpu coloured in red. Would be awseome for a future episode to talk about why it's written as "08 00 00 00" instead of "00 00 00 08". Love watching your videos, they refresh my memory a lot!
Definitely going to cover that... eventually :)
Thank you for your reply, much appreciated!
Isn't it big endian vs little endian?
they are read backwards
It is that bytes are saved in inverted order
Your PC can only manipulate bytes (8bits) and not single bits
Each byte has it's own place and name
So when you wanna read a number that is bigger than a byte you will need to acces two "places"
So let's assume we save F7 65 (this takes up 2 bytes, Hexadecimal is designed so that each number equals 4 bits so two make up one byte that's why they are speperated like this) in what is called FE0037
It will use FE0037 and the next one (in this case FE0038) to save the number
But now what if we wanna read this in 8 bit instead of 16 bit mode (16 bit is when we use 2 byte, 8 when a single one)
So let's read FE0037 (the smaller one)
If it were saved in normal order we would end up with F7 which in no way equals F7 65. It equals that as much as 60 equals to 6054.
Better it would be to get 65 which does have euqal the lower part of the number, just like how 54 is 6054 minus 6000.
And that's why we save this 65 on the byte we accesed. It makes accessing that byte again in a different processing mode more logical instead of having to think about in what mode you were and from there count upwards to which byte you have to acces to get a somewhat logical representation.
thank you...i was a bit scared to play with memory and debugging but now i feel a bit confident. great video and thanks for codelite too. Its a nice simple ide
Thanks for this great series cherno loved your content even though not going to use in Game Dev, but still helped a lot:)
This is gold. I just started to learn C++ and I love it. Thank you 🙏
this has changed everything for me
Hi. Are you going to make episode about const keyword? I've been always struggling to understand why and how things can go wrong if not using them.
Yep, absolutely
My prof loves throw const combinations with us just to fuck with us!
it's 2024 and I'm watching this wonderful series after 6 years, and I have no idea what Cherno is doing these days, but I hope he's doing great
Hi Cherno. I just loved this series. Its a great fun. Please continue with this. Currently I will not be able to pay but definitely a lot of love n respect for what you are offering.
that's so incredible, U let me know lots of detail knowledge in C++
Liked, subscribed, commented, and speeding towards the Game Engine series. Great vid, keep up the stellar work!
I literally took around 2.5 hours to make notes of this video. Thank you so much.
Just a point of note: You need to be in debug mode in order to open the memory window. It means you place a break point, start debugging and then go to the menu Debug -> Windows to see the Memory option. I couldn't find it and a simple search revealed this fact. When Cherno opened the memory window, he was already in the debug mode.
dude you saved my life, I freaked out to do not find that memory menu option
😘❣
He did mention that in the video.
This is so amazing!! Perfectly executed explanation. :)
This video should be the prerequisite for introduction to programming lectures in college to understand what we are going to do . Thanks for fascinating explaining
Thanks for your work bro i learn a lot of your videos i never find a good tutorial fo visual studio and yours are the best regards
Dude, how many guitars do you possess ? x)
Not enough ;)
Han Solo if you have asked me that question, I would have replied "too many." Lolol. I sell guitars in my mother's shop. I wish I could learn to play guitars, yet I have never touched any guitar in my family's shop. I just never get the time for guitar tutorials.
Han Solo I don't really own all the guitars in my family's shop. I was only joking in my last comment. I felt rich which I said "too many." I can write music only in my head and I would love to put that on paper or on musical instruments. I can play piano only just a little, but I don't get free time for myself. Besides I have other hobbies in the evenings and on lazy Sunday. Someday, I will get around to learning guitar or ukulele.
Dude and possess don't go well in the same line
It's never enough :D
Best C++ videos on youtube, love this series, hope there's more
The only thing i wish these youtube tutorials would do, is provide some exercises for each video with an answer key (if one wants to look). I listen to the video, I am pretty sure i understand it but i guess i just need the confirmation that I have grasped the essence of what is being taught in each video. I am not complaining as i am in the beginner stages of learning so, what would i know?. Anyways, liked and subscribed.
P.S There is something about the cool color gradients and the soft music in the background of these videos that keeps me coming back.
My breakpoints simply were ignored because the optimization was set on speed. Disabling optimization solved the issue.
hey guys I am using vs2022 and I found that when I set break points inside the main function as shown in the video, it is not paused as expected, it will just continue. But my breakpoint is a solid red point which means it is a valid breakpoint.
maybe it is due to some previous set up in previous videos... idk .. Finally I tried just creating a new project and now it works.
Thank you so much. It has been super helpful. I enjoyed watching these series of videos.
Hey make sure that at your settings you have optimizer disable.. i fall for that one
Excellent! I'm learning a lot with your series! Please keep it up!
Cherno please I need to know what's the background music starting at 6:24
Anyway love this series so much. More deep knowledge of c++ about how it works
Wow... I'm re-watching this in 2022 and it's amazing how good you are at explaining things.
I'm blown away. Good job mate, and thank you.
Thank you once again for the awesome content!!! (your hair is amazing, dam)
You can also CTRL+F10 and it will run to where the current line where the cursor is. Use that all the time, makes "regular" breakpoints almost useless.
I think we are at a point where people who have no idea about programming have stopped watching. So there wouldn't be too much point in covering very basic stuff like for loops and if statements. Keep up the good work!
Adhyyan He gets to the bottom of everything. It creates a solid base to work from. You could learn something you had no idea you didn't know. It's worth the listen to me. But then again I'm still pretty new. Still here tho. I'm for real trying to learn this so I definitely appreciate the details. I get how it might get boring if you already know most of this but he did say at the beginning that he wanted to create a thorough c++ course that teaches people everything they need to know to create clean, fast code. So hey hey I'm still here don't ya dare take them details away from scrubs like me. Lol
And yet, about no one noticed he got the order of execution wrong lol... it increments before checking the condition while he says that it checks then increments.
Omg the orange guitar is actually an ideally looking electric guitar that i dream about.
Edit: This video has to watch every programmer in the world by my opinion. i did not know anything about "cc". Thank you, Cherno!
Thank you for these series
Fantastic stuff! Great quality video and information. Much appreciated!
Hello, I have a problem at around 10:30 when you start explaining the memory, to be precise where it shows the hexadecimal values of a, and here you got all cc values, where I got values for variable a: b5 3b 1f ...etc. Is there some setting that I may have missed?
Nvm fixed it, I had some problems with the properties of the project. I went back to "How C++ works" and just copied the settings from Cherno that he just blazed thru them and it fixed it for me. UA-cam 0.25 speed helped me with the pausing between those fast frames xD
For some reason when I hover over "message" like at 6:37 Visual Studio tells me "Error reading characters of string" o.o What's wrong? My code appears to be exactly the same as his.
Hi! Is there possible to debug a dll made in C++ with a makefile? Like having a program to invoke the dll and then debug it? Or how to debug the dll?
bucky and thecherno
piano sound in background is so freaking nice
so much to learn from your videos thanks again.
What kind of music is used for this video? Is there a playlist?
Wonderful session
@16:52 You said, you'll talk about the value of variable (c) persisting even though it had gone out of the scope, but you didn't.
Is there unit test in c++ , is there a video on it ?
Really incredible stuff even years later thanks!
This tutorial is really exciting! Cheers!
I have never seen so many guitars in one's house before. You should do a guitar learning series!
Wow this is the best video of the basis of debuging
This series is fantastic. I noticed that you mentioned the default value before initialization in debug mode will be 0xcc, and I just curious is that fits for all debugging tools or just Visual Studio? Since I've tried this in gdb and found the value is not 0xcc...
Hey, for start props! amazing tutorial.
Quick question, I am following exactly your steps, but I do not get a bunch of cc in the memory space of my "a" variable (memory1). However when I continue the code it gets assigned the correct value. Why is that? Does that mean I do not purge the memory prior to assigning a value?
8:33 Can we appreciate how fast he managed to write this for loop... WOW
At 8:55, the arrow keeps passing "int a = 8;" when I start the debugger. I'm not sure how to check the value of "a" either. Information on what's happening would be appreciated.
0xcc is opcode for software interrupt INT3 used by the debugger
love your vids,full with interesting details
Chuck Norris does not use debugger to debug his code, he stares the code down until the code confesses.
thank you for the incredible videos you make!
I absolutely love your work !
this video helped me a lot because with breakpoints i learned how to find my mistakes even if it is very small
thanks the cherno
very helpful bro, just subscribed!