Let us set another breakpoint on line 15 and then continue the program until it hits that breakpoint. As we step through the program, and eventually reach the end of the bar function, the list of local variables gets longer, i.e. The Variables view now shows us what local variables we have in this function and what their current values are. We are now paused on the first line of the bar function: Lets click once on Step Over and then Step Into. At the top of the text editor we now see a toolbar with commands for common debug actions: Continue, Step over, Step Into, Step Out etc. We can also see where we are in the call stack and a list of all breakpoints. The yellow line shows us the location that we will execute next if we continue to run the program. When the program reaches line 11, it will pause: Next we start the program again (either by clicking on Run and Debug or pressing F5). The red dot shows us that we have now set a breakpoint. We do this by simple clicking with the mouse in the left most column of the code editor: Lets make this example a bit more useful by setting a breakpoint on line 11. In this example the whole program ran through in one go and finished without any problem. Output is displayed in the Julia Debug terminal. Click Run and Debug (or select F5) to run the active Julia file in the debugger.You will now see the default debugger start panel: The Julia extension supports debugging of all types of Julia programs and applications.įor general debugging features such as inspecting variables, setting breakpoints, and other activities that aren't language-dependent, review VS Code debugging.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |