1 00:00:00,330 --> 00:00:09,960 So once you add a brief point, now we if you perform an execution of a OK that run launch on the highway. 2 00:00:10,350 --> 00:00:14,180 So this won't add the information related to break point. 3 00:00:14,200 --> 00:00:19,730 So you'll be finding our program will not be suspended anywhere on the break point. 4 00:00:19,740 --> 00:00:20,100 OK? 5 00:00:20,520 --> 00:00:23,180 It will be still running till then. 6 00:00:23,250 --> 00:00:25,530 Again, we are able to see a value of 300. 7 00:00:25,600 --> 00:00:33,120 OK, so you could clearly see when you perform or so we do not send the information or break point information 8 00:00:33,120 --> 00:00:38,000 along with identifying, and we won't be able to perform a duplicate right. 9 00:00:38,310 --> 00:00:38,670 So. 10 00:00:39,630 --> 00:00:42,570 We have a separate perspective to handle that. 11 00:00:42,760 --> 00:00:46,470 But again, that is what we would do as a DBA perspective, right? 12 00:00:46,800 --> 00:00:50,700 So here on the top, you could see we have an open perspective. 13 00:00:50,700 --> 00:00:53,800 So this will reflect all the perspective that we have. 14 00:00:53,820 --> 00:00:56,670 And by default, it is C and C++. 15 00:00:57,450 --> 00:01:02,280 So here you could develop your C and C++ applications. 16 00:01:02,610 --> 00:01:04,860 And then you also see a file hierarchy. 17 00:01:04,950 --> 00:01:05,280 OK. 18 00:01:05,580 --> 00:01:12,960 So this is what we do in the C++, C and C++ specific to the next specific do that we have is a debug 19 00:01:12,960 --> 00:01:13,860 prospect, right? 20 00:01:13,890 --> 00:01:19,460 So the best way to enter into DevOps perspective is just select the folder you where you have your main 21 00:01:19,470 --> 00:01:25,470 application, right click now instead of selecting Run as you select, debug and launch on hardware. 22 00:01:25,830 --> 00:01:31,950 So this will ask us whether you want to switch to debug perspective or just hates, and then you'll 23 00:01:31,950 --> 00:01:33,750 be into a debug perspective. 24 00:01:33,840 --> 00:01:34,110 Right? 25 00:01:34,470 --> 00:01:40,260 So we'll just be going through the various windows that we have so that as we progress further, will 26 00:01:40,260 --> 00:01:44,990 be predominantly degrade and execution of the rate. 27 00:01:45,270 --> 00:01:48,760 So here you could see all the information related to the processor. 28 00:01:48,790 --> 00:01:53,820 OK, so the session that we are in and the process which is currently executed down the hierarchy of 29 00:01:53,820 --> 00:01:58,500 the functions that we have to have inside our main application, right? 30 00:01:59,490 --> 00:02:06,420 Second one here we have multiple win, right, so valuable window will reflect the variable that we 31 00:02:06,420 --> 00:02:08,770 have in our main goal. 32 00:02:09,060 --> 00:02:15,260 So as we execute our goal, we could analyze the values of variable in a real rate. 33 00:02:15,270 --> 00:02:17,010 So this is what you could see here. 34 00:02:17,310 --> 00:02:19,800 You also have a breakpoint v rate. 35 00:02:19,800 --> 00:02:25,880 So this will reflect all the lines where you have added a break. 36 00:02:26,430 --> 00:02:32,910 So in fact, it could also show you where you have added a breakpoint and then later on you disable 37 00:02:32,910 --> 00:02:32,980 it. 38 00:02:33,270 --> 00:02:39,720 So you could also see disabled breakpoint as well as people in are looking to be pointing to the rest 39 00:02:39,720 --> 00:02:42,920 of the thing we will be understanding as we roll this spot. 40 00:02:43,050 --> 00:02:43,350 Right? 41 00:02:44,160 --> 00:02:51,150 Then we have this assembly view right to where you would analyze the code in an assembly language, 42 00:02:51,150 --> 00:02:51,450 right? 43 00:02:51,450 --> 00:02:54,360 So that is the third window, which is very, very useful. 44 00:02:54,720 --> 00:03:01,140 OK, then you could see a mean window where we have our application, which we'll be testing on and 45 00:03:01,200 --> 00:03:01,940 speaking, right? 46 00:03:01,950 --> 00:03:02,520 So here. 47 00:03:03,450 --> 00:03:13,320 The green color basically highlight our audition of a pointer, right, so our execution of a CPU processor 48 00:03:13,320 --> 00:03:17,250 is been suspended over here or it has been passed over here. 49 00:03:17,680 --> 00:03:20,470 OK, we have our breakpoint. 50 00:03:20,550 --> 00:03:27,180 So as long as now we do not use the break point option that we have, we won't be moving ahead. 51 00:03:27,430 --> 00:03:32,200 So this allows us to debug the specific logic that users want to test. 52 00:03:32,220 --> 00:03:41,160 OK, so we will be pausing our execution of our process at the specific point where you have added the 53 00:03:41,160 --> 00:03:47,430 breakpoint and then we will be dynamically controlling the execution by the various option that we have 54 00:03:47,730 --> 00:03:49,170 in this perspective, right? 55 00:03:50,010 --> 00:03:57,460 So the code highlighted with the green will basically represent the point where I see CPO execution 56 00:03:57,460 --> 00:03:58,350 response rate. 57 00:03:59,750 --> 00:04:03,950 Then we could also have to get a million lower here. 58 00:04:04,010 --> 00:04:10,160 OK, so all the information that you would be sending out to cancer could be visualized over here. 59 00:04:10,200 --> 00:04:10,550 OK? 60 00:04:10,880 --> 00:04:13,520 We also have a memory and a sticky log. 61 00:04:13,760 --> 00:04:19,790 So here you analyze all the information, the important messages related to LSD. 62 00:04:19,920 --> 00:04:20,180 Right? 63 00:04:21,160 --> 00:04:27,340 Along with that's just next to our world, we could also see an outline of all various shriver as well 64 00:04:27,340 --> 00:04:29,950 as a function that we have in our right. 65 00:04:30,220 --> 00:04:35,740 So these are some open windows, which will be our understanding as we progress further with a point. 66 00:04:36,070 --> 00:04:41,860 So here we will see all the information related to a function hierarchy, as well as the session for 67 00:04:42,080 --> 00:04:45,640 the session and the code in which we are executing our code. 68 00:04:46,210 --> 00:04:52,600 All the information related to a values of a variable could be analyzed in this valuable chart and all 69 00:04:52,600 --> 00:04:53,950 the breakpoint that we have. 70 00:04:53,950 --> 00:04:59,920 I mean, program could be analyzed over here, right to rest of the things will be understanding as 71 00:04:59,920 --> 00:05:01,000 we progress further. 72 00:05:01,660 --> 00:05:04,480 Here we get the mean application. 73 00:05:04,600 --> 00:05:10,960 OK, so the constructs which are highlighted with a green color, represent the. 74 00:05:11,980 --> 00:05:13,780 Condition there are pointer. 75 00:05:14,760 --> 00:05:22,550 Of the prosthetist boss straight, so after this, we could dynamically control the execution of a person. 76 00:05:23,200 --> 00:05:27,570 These also represent the point at which user have added a breakpoint, right? 77 00:05:28,200 --> 00:05:35,010 Then outline highlights all the function, size, bells and chamber that we have in our pool. 78 00:05:35,400 --> 00:05:43,020 OK, finally, sticky law could be used to analyze an important message related to an SDK, and we also 79 00:05:43,020 --> 00:05:45,270 have an SDK terminology, right? 80 00:05:45,780 --> 00:05:50,790 So these are some of an option that we have with the debug perspective, right? 81 00:05:50,790 --> 00:05:55,270 And here you could really see the energy perspective, right? 82 00:05:55,350 --> 00:05:59,670 So previously that used to be on C or C++ perspective. 83 00:05:59,920 --> 00:06:02,190 Here we are on the debug perspective.