So once you add a brief point, now we if you perform an execution of a OK that run launch on the highway.
So this won't add the information related to break point.
So you'll be finding our program will not be suspended anywhere on the break point.
OK?
It will be still running till then.
Again, we are able to see a value of 300.
OK, so you could clearly see when you perform or so we do not send the information or break point information
along with identifying, and we won't be able to perform a duplicate right.
So.
We have a separate perspective to handle that.
But again, that is what we would do as a DBA perspective, right?
So here on the top, you could see we have an open perspective.
So this will reflect all the perspective that we have.
And by default, it is C and C++.
So here you could develop your C and C++ applications.
And then you also see a file hierarchy.
OK.
So this is what we do in the C++, C and C++ specific to the next specific do that we have is a debug
prospect, right?
So the best way to enter into DevOps perspective is just select the folder you where you have your main
application, right click now instead of selecting Run as you select, debug and launch on hardware.
So this will ask us whether you want to switch to debug perspective or just hates, and then you'll
be into a debug perspective.
Right?
So we'll just be going through the various windows that we have so that as we progress further, will
be predominantly degrade and execution of the rate.
So here you could see all the information related to the processor.
OK, so the session that we are in and the process which is currently executed down the hierarchy of
the functions that we have to have inside our main application, right?
Second one here we have multiple win, right, so valuable window will reflect the variable that we
have in our main goal.
So as we execute our goal, we could analyze the values of variable in a real rate.
So this is what you could see here.
You also have a breakpoint v rate.
So this will reflect all the lines where you have added a break.
So in fact, it could also show you where you have added a breakpoint and then later on you disable
it.
So you could also see disabled breakpoint as well as people in are looking to be pointing to the rest
of the thing we will be understanding as we roll this spot.
Right?
Then we have this assembly view right to where you would analyze the code in an assembly language,
right?
So that is the third window, which is very, very useful.
OK, then you could see a mean window where we have our application, which we'll be testing on and
speaking, right?
So here.
The green color basically highlight our audition of a pointer, right, so our execution of a CPU processor
is been suspended over here or it has been passed over here.
OK, we have our breakpoint.
So as long as now we do not use the break point option that we have, we won't be moving ahead.
So this allows us to debug the specific logic that users want to test.
OK, so we will be pausing our execution of our process at the specific point where you have added the
breakpoint and then we will be dynamically controlling the execution by the various option that we have
in this perspective, right?
So the code highlighted with the green will basically represent the point where I see CPO execution
response rate.
Then we could also have to get a million lower here.
OK, so all the information that you would be sending out to cancer could be visualized over here.
OK?
We also have a memory and a sticky log.
So here you analyze all the information, the important messages related to LSD.
Right?
Along with that's just next to our world, we could also see an outline of all various shriver as well
as a function that we have in our right.
So these are some open windows, which will be our understanding as we progress further with a point.
So here we will see all the information related to a function hierarchy, as well as the session for
the session and the code in which we are executing our code.
All the information related to a values of a variable could be analyzed in this valuable chart and all
the breakpoint that we have.
I mean, program could be analyzed over here, right to rest of the things will be understanding as
we progress further.
Here we get the mean application.
OK, so the constructs which are highlighted with a green color, represent the.
Condition there are pointer.
Of the prosthetist boss straight, so after this, we could dynamically control the execution of a person.
These also represent the point at which user have added a breakpoint, right?
Then outline highlights all the function, size, bells and chamber that we have in our pool.
OK, finally, sticky law could be used to analyze an important message related to an SDK, and we also
have an SDK terminology, right?
So these are some of an option that we have with the debug perspective, right?
And here you could really see the energy perspective, right?
So previously that used to be on C or C++ perspective.
Here we are on the debug perspective.