So in the studio, we're going to talk about those people in the program, so if you have two hundred
thousand two hundred lines of court, if you want to check out the content, you this is the point of
sale here.
And then you print the will and you will see whether the program is going correctly or not.
That's a basic way of determining any errors.
And actually, it's very tough when you have long court like 300, 400 lines of code and tolerance of.
And in that, uh, if you have those code and you just putting up shipments everywhere is very bad.
And it's also time consuming and it's a waste.
So that's why we need to be able to program.
So what this means is you can stop the program at a certain point and you can inspect the contents up
to that point, and then you can chip through the program called one one instruction per day.
So now we are going to do this now quick on this here.
There is a place and it has a hidden section, but there is the bug and this is the debugger.
And if you click on this sideboard open and click on this romantical and it will ask what to do with
that file.
So we need to see this pattern, currently active python working on this one.
And you can see there are some controls here.
So this one is the pause button.
OK.
Now, this program has been executed directly because we did not set the breakpoint.
So this breakpoint, whenever it was hit by the Python interpreter, the program for us stops.
Sorry, sir.
I'm going to set the breakpoint just before this for you can set the breakpoint here.
Uh, you can see the, uh, right to this box and you can see there is a column and you can set the
red dot and it says Bridgepoint.
Now, what I want to do is I want to run this now program and execute this line.
But at starting up this right, it will wait for it to execute.
So we need to manually step through this are the order of the court.
Now, let me run.
And David, going on despite pattern.
Now, as you can see, there is a little color line indicating that the U.S. is going to be this one,
and if you expand here, we got the local news that is Al Elizalde, and it is a variable containing
the values of this, uh, content of any of these values.
So you can see l can condense all this, uh, function variables and you can see index on and all those
variables.
Now, what you want is I want to do this program.
I want to execute for only once.
So these are the controls.
I can control the program.
So if you click on this continues, the program continues to the end.
And if there is any breakpoint, then it will stop there.
And this one is a step over.
If you don't want to hear this one, you can step over this.
If there is a function here and you're going to step over the function, you need not go to this function.
So if you want to step into it, we step exactly one instruction.
And if you are reading inside the thousand lines of code of a function, then if you want to step out
of that function, you can see what this is, the restart and this is a stop.
Now, I'm going to step into now this instruction gets a good.
Now, if you can see, I bet you used.
And next U.S., I am going to print it and it is going to be if I click on this, uh, step into print
of a love I love, that is now a we get printed, as you can see, the output.
The city certainly can also see the cards stacked here.
And now we are going to use this again because it will exist until the end of this, uh, list.
Now, I'm going to go this step into step again.
You can see the second world now in that same way, you can print out the elements, step into step
in twos and step two times to print one element.
And now this condition is going to be checked Ivory's fight and then tough and off.
This list is six and this is it we take with.
So, no, it will get out of this for now.
As you can see, this instruction pointer is pointing to is crucial to know if you go a step into this,
we can see a new word has been added, easy to do.
And if we step through this again, we use too far.
Now, the if condition is going to be it is going to be close to find if you are greater than be.
So it is not going to be that way to pass to the next condition to step into this.
You can see this statement is not executed because he he's not resentful against each other.
Is course to be A and B are both equally into this now.
It will get out of this.
Uh, it is wrong because these two conditions fail and of course, is will execute every condition other
than this one.
And I will go to print nothing.
I will.
As you can see, our program director has been closed.
So that's sad about this.
I hope you have understood.
So don't worry, I will include, uh, uh, this Windows expert and also assembly language.
Then you will get much more idea of debugging.
But this is generally the high level.
You just put the breakpoint over here and then you step into this program.
Now, I want to show you this.
I will also say that if before if I am going to run any current pattern for.
So now I'm going to.
On this one, I'm getting three values, so now if I want to leave out of this, I can just simply continue
and continue will go on continuing our or the core.
And if there are any requirements, it will stop there.
Now, let's continue.
So at this point, OK, no, as you can see out the open then it has been, uh, program has been paused
here because this is the breakpoint point.
I continue here, the program.
Just print out the print and I nothing just continuing the program.
So that's what I hope we have understood that in the breakpoints and, uh, skipping through the program
that sorry about that.
This is very important.
And when you have written so much lines of code and then worrying about the, uh, available input,
so this debugging is used for, uh, solving these logical errors.