WEBVTT - This file was automatically generated by VIMEO 1 00:00:07.700 --> 00:00:10.800 Hello and welcome back to another video from section 2 00:00:10.800 --> 00:00:13.600 8. And as you advance step, this course 3 00:00:13.200 --> 00:00:16.200 will in this video actually going to talk about a 4 00:00:16.200 --> 00:00:16.700 little bit. 5 00:00:17.900 --> 00:00:20.200 More specific things. And I do 6 00:00:20.200 --> 00:00:23.700 feel Information Technology film Coatings. And also, 7 00:00:23.700 --> 00:00:26.100 we're gonna pay attention to, what is debugging or is 8 00:00:26.100 --> 00:00:29.500 troubleshooting, because it's really important. If you're doing any 9 00:00:29.500 --> 00:00:32.300 field in Information, Technology Program review, 10 00:00:32.300 --> 00:00:35.300 our security engineer for our 11 00:00:35.300 --> 00:00:38.200 network engineer, no matter is always going to come 12 00:00:38.200 --> 00:00:42.200 to you, and it's going to help you, or what 13 00:00:42.200 --> 00:00:46.300 are you? So, let's have an overview of new Concepts. Exactly. 14 00:00:45.400 --> 00:00:47.400 And what is it? Exactly? 15 00:00:48.700 --> 00:00:51.400 So we get a pin entry subjects. First. What 16 00:00:51.400 --> 00:00:54.400 is the stepson of debugging process? And what 17 00:00:54.400 --> 00:00:57.500 is the best debugging techniques and 18 00:00:57.500 --> 00:01:00.700 how do I get back? Well, it's 19 00:01:00.700 --> 00:01:03.300 the replication these days need to renew, be 20 00:01:03.300 --> 00:01:06.400 error free before I going out in the market, for sure. If 21 00:01:06.400 --> 00:01:07.400 you want to release them. 22 00:01:08.400 --> 00:01:11.200 Tools or application, doesn't should 23 00:01:11.200 --> 00:01:14.700 be have any ruin. It. You should be completely without 24 00:01:14.700 --> 00:01:17.400 any error and error less to 25 00:01:17.400 --> 00:01:20.500 run complete without any glitch 26 00:01:20.500 --> 00:01:23.300 or something like that. So, customers have 27 00:01:23.300 --> 00:01:27.200 difficulties among the most important things in the market 28 00:01:26.200 --> 00:01:29.200 and running positions, or your supervisors at 29 00:01:29.200 --> 00:01:32.700 this vacation, but only a bug. Free product, can keep 30 00:01:32.700 --> 00:01:35.000 your customer or a supervisor happy. 31 00:01:36.100 --> 00:01:39.700 In this video. I'm going to talk about a little bit debugging and how it's different 32 00:01:39.700 --> 00:01:42.400 from suffer. Just imagine that 33 00:01:42.400 --> 00:01:45.400 they have different between you or software developers. That when 34 00:01:45.400 --> 00:01:48.300 you are developing a tool for 35 00:01:48.300 --> 00:01:51.500 your company, for example, suit your supervisors Pacific Gas, 36 00:01:51.500 --> 00:01:54.200 Co your fitness center and customers specifically asked 37 00:01:54.200 --> 00:01:57.800 you to run or cray, Tennessee, tools or 38 00:01:57.400 --> 00:02:00.800 the tool related to the end map in 39 00:02:00.800 --> 00:02:03.800 Python. So caution 40 00:02:03.800 --> 00:02:05.200 or dividing it refers. 41 00:02:05.300 --> 00:02:09.000 Starting defying analyzing any moving errors. This 42 00:02:08.400 --> 00:02:11.300 process begin after a software fails to 43 00:02:11.300 --> 00:02:14.900 execute probably and conclude by solving the problem and 44 00:02:14.900 --> 00:02:17.800 successfully testing the software but 45 00:02:17.200 --> 00:02:20.500 it is considered to be an extremely complex 46 00:02:20.600 --> 00:02:23.200 and tourist ask because they're need 47 00:02:23.200 --> 00:02:27.400 to be resolved. All the stages of debugging to 48 00:02:27.400 --> 00:02:30.600 make sure that you don't have any problem getting 49 00:02:30.600 --> 00:02:33.200 out with at the end. So why do we need 50 00:02:33.200 --> 00:02:34.200 to buy? Exactly? 51 00:02:35.100 --> 00:02:38.500 The process of debugging begin as soon as the code of suffers writing 52 00:02:38.400 --> 00:02:41.600 then is continue to successfully State 53 00:02:41.600 --> 00:02:44.100 as a skoda has combined with other units of 54 00:02:44.100 --> 00:02:48.300 a programming or performing. A task to 55 00:02:48.300 --> 00:02:51.500 form a software product debugging has many 56 00:02:51.500 --> 00:02:54.900 benefits such as if you pause an error condition, immediately 57 00:02:54.200 --> 00:02:57.800 those earlier detection whenever and 58 00:02:57.800 --> 00:03:00.500 make the process and software developers testers 59 00:03:00.500 --> 00:03:03.200 for and this is 60 00:03:03.200 --> 00:03:03.800 forceful. 61 00:03:04.500 --> 00:03:07.400 They also provide maximum useful information of 62 00:03:07.400 --> 00:03:10.800 data structure and always, always easy, 63 00:03:10.900 --> 00:03:13.600 enter production, the bargaining 64 00:03:13.600 --> 00:03:16.600 sister developers in reducing useless and distracting 65 00:03:16.600 --> 00:03:19.600 information on search for debugging. 66 00:03:19.600 --> 00:03:22.700 Developing can avoid complex. 67 00:03:22.900 --> 00:03:25.500 One use testing code, save 68 00:03:25.500 --> 00:03:28.500 time and also energy in sub developments. 69 00:03:30.300 --> 00:03:33.500 So what is this tips? Different steps involved 70 00:03:33.500 --> 00:03:36.700 in the process of debugging are in the following slide. 71 00:03:36.500 --> 00:03:39.200 First of all, is identify an error to 72 00:03:39.200 --> 00:03:42.800 find out? What is our problem? Exactly, which one exactly. 73 00:03:42.100 --> 00:03:45.100 Then of finder location and 74 00:03:45.100 --> 00:03:48.100 eternal level is analyzing the error, why is it 75 00:03:48.100 --> 00:03:51.700 happening and why we drunk and then prove analyzes and 76 00:03:51.700 --> 00:03:54.300 been covered earlier or damage? And 77 00:03:54.300 --> 00:03:57.500 I did end of the line. We're going to fix 78 00:03:57.500 --> 00:03:58.600 it and 79 00:03:59.900 --> 00:04:01.600 Make sure it works correctly. 80 00:04:02.800 --> 00:04:05.200 So the first is the, we have a better indication of an 81 00:04:05.200 --> 00:04:08.500 error can lead to wasted. Development time is usually that 82 00:04:08.500 --> 00:04:11.800 production are reported by user and hard to introduction. Something 83 00:04:11.100 --> 00:04:15.300 that information will receive is misleading. So 84 00:04:15.300 --> 00:04:18.600 it's very important to you identify the actual 85 00:04:18.600 --> 00:04:22.400 error because is always could be misleading 86 00:04:21.400 --> 00:04:24.400 for you. Trust me. If 87 00:04:24.400 --> 00:04:27.400 you do not understand the error, you're going to be wasting your 88 00:04:27.400 --> 00:04:28.700 time the whole day. 89 00:04:29.900 --> 00:04:32.400 And the second level we have find their 90 00:04:32.400 --> 00:04:35.300 location, says the same as the first. 91 00:04:35.300 --> 00:04:38.100 One after identifying are correctly. You need to 92 00:04:38.100 --> 00:04:41.200 go through their code and to find exact line. And 93 00:04:41.200 --> 00:04:44.300 despite that you make data or for yourself. And 94 00:04:44.300 --> 00:04:47.600 we need to understand why we did it. Analyzing it 95 00:04:47.600 --> 00:04:50.400 in the third step, you need to use butter 96 00:04:50.400 --> 00:04:53.400 approach from the error location lies. The code is 97 00:04:53.400 --> 00:04:56.400 help. You to understanding error, analyzing about 98 00:04:56.400 --> 00:04:59.100 has two main goals such as checking around. 99 00:04:59.700 --> 00:05:02.100 Her father was to be found and to 100 00:05:02.100 --> 00:05:06.000 make sure about a risk of entering a cortical damage. 101 00:05:07.300 --> 00:05:10.700 And we haven't put in license. Once you're done. I 102 00:05:10.700 --> 00:05:13.100 like the unoriginal bug. You need to find a 103 00:05:13.100 --> 00:05:16.500 few more hours and made a always when you fixing 104 00:05:16.500 --> 00:05:19.500 bugs, is going to be more bugs, after that. Trust 105 00:05:19.500 --> 00:05:22.600 me about it. Then we have the cover letter 106 00:05:22.600 --> 00:05:25.400 all damage in this stage. You need to create 107 00:05:25.400 --> 00:05:28.100 a getter of all in States, for the code, the way 108 00:05:28.100 --> 00:05:29.500 you're going to make change. 109 00:05:30.600 --> 00:05:33.200 End of the level we're going to fix any 110 00:05:33.200 --> 00:05:36.100 validate. The phone stages to fix all the 111 00:05:36.100 --> 00:05:39.700 errors and run the test script checketts and it worked or 112 00:05:39.700 --> 00:05:42.400 not. So it's very important to study 113 00:05:42.400 --> 00:05:46.000 the system in a different. In order to understand the system. It's 114 00:05:45.500 --> 00:05:48.900 healthy Burger to conduct different representative 115 00:05:48.900 --> 00:05:52.000 of the system's already bugged. So 116 00:05:51.200 --> 00:05:54.500 there's a lots of debugging Tools in 117 00:05:54.500 --> 00:05:57.500 programming and computer programming to test 118 00:05:57.500 --> 00:05:59.600 the debuggers for other programmers. 119 00:05:59.700 --> 00:06:02.500 Is there are a lot of public domain software 120 00:06:02.500 --> 00:06:05.700 is like GD P and D Peaks 121 00:06:05.700 --> 00:06:08.400 that you can use for debugging. Also they 122 00:06:08.400 --> 00:06:11.800 offer console-based common line and interface and 123 00:06:11.800 --> 00:06:14.300 again, it depends on you. Which one are you more 124 00:06:14.300 --> 00:06:17.400 comfortable wins? As a previous video editor 125 00:06:17.400 --> 00:06:21.100 section. We saw then map towards a graphical and 126 00:06:20.100 --> 00:06:23.400 we saw nmap that command line 127 00:06:23.200 --> 00:06:26.300 based on you. So this list of the 128 00:06:27.500 --> 00:06:30.600 Debuggers such as red are to win, debug 129 00:06:30.600 --> 00:06:34.000 or ring W, indigo2 130 00:06:33.500 --> 00:06:36.800 or well green, which 131 00:06:36.800 --> 00:06:39.800 is we can have to find out errors of an article in 132 00:06:39.800 --> 00:06:42.400 the web. So I hope you understand what is debugging in 133 00:06:42.400 --> 00:06:44.700 different stages involved in this program for your buck. 134 00:06:45.900 --> 00:06:48.200 Let's have a summer in our video. First of 135 00:06:48.200 --> 00:06:51.600 all, we talked about finding box analyzing understand why by 136 00:06:51.600 --> 00:06:55.000 backward and fixing removing box. This 137 00:06:54.400 --> 00:06:57.800 debugging techniques is a traced base debugging 138 00:06:57.800 --> 00:07:01.000 is traditional and most common debugging technique. Use 139 00:07:00.200 --> 00:07:03.400 it most debugging tools or a tray 140 00:07:03.400 --> 00:07:06.900 space. The bargains are protected and concept of breakpoints. 141 00:07:06.600 --> 00:07:09.400 At the end, debug is going 142 00:07:09.400 --> 00:07:12.700 through to cool flow during the runtime. Whereas tracing 143 00:07:12.700 --> 00:07:15.500 is giving the details of execution plan process. 144 00:07:15.600 --> 00:07:18.300 Time, meaning details. The next video should 145 00:07:18.300 --> 00:07:21.700 be first video after 4 section 9 on lysing. 146 00:07:21.800 --> 00:07:22.400 Good luck.