Shulou(Shulou.com)06/02 Report--

This article will explain in detail the solutions to the failure of vscode lua breakpoints. The editor thinks it is very practical, so I share it for you as a reference. I hope you can get something after reading this article.

What if the vscode lua breakpoint fails?

Debugging Lua tutorials using VSCode breakpoints

one。 Install Visual Studio Code (vscode) and plug-in Center search install luaide

two。 Configure luach.json

1. Just drag the project folder directly into vscode.

two。 Debug icon-> Settings-> Select LuaDebug in the left column, and the launch.json file will appear

3. Find the exePath field in the launch.json file and modify it to the simulator path

For example: "exePath": "D:/xxx/player-3.x/player3.exe"

Other places can be configured by default.

III. Lua breakpoint debugging configuration

1. Download the LuaDebug.lua file

Address: https://github.com/k0204/LuaIde

two。 Put the LuaDebug.lua file in the project src directory

3.。 Debug code addition

Add the following code to the main.lua file:

Local breakInfoFun,xpcallFun = require ("LuaDebug") ("localhost", 7003)-3.x-- 1. Breakpoint timer add cc.Director:getInstance (): getScheduler (): scheduleScriptFunc (breakInfoFun, 0.3, false)-- 2. Program exception listener function G__TRACKBACK (errorMessage) debugXpCall () Print ("-") local msg = debug.traceback (errorMessage 3) print (msg) print ("- -") end local status, msg = xpcall (main, G__TRACKBACK)-- if 2.x CCDirector:sharedDirector (): getScheduler (): scheduleScriptFunc (breakInfoFun, 0.3) False) function G__TRACKBACK (errorMessage) debugXpCall () Print ("-") local msg = debug.traceback (errorMessage 3) print (msg) print ("-") end local status, msg = xpcall (main, G__TRACKBACK)

four。 Debug:

1. Press F5 to start debugging

Once debugging is started, the debug command bar is displayed at the top of the editor

Continue / pause F5

Skip F10

Enter F11

Exit Shift+F11

Restart unassigned

Stop debugging Shift+F5

two。 Click the debug icon on the left view bar of the VS Code to open the debug view.

3. Some debugging tips

The variable area can not only see the value intuitively, but also can edit the variable value debugging directly, or edit it over the source code in the editor by hovering over the mouse.

2 if you want to track a variable all the time, you can edit that variable to monitor.

3 using the call stack, you can know who makes an error when the error function is called. Layer by layer, you can sometimes guess the cause of the error.

4 in cases where the source code is not available but the function name is already known, you can create a breakpoint function by pressing the + in the header of the breakpoint area.

five。 Edit user code snippet (Snippets)

Menu bar-> File-> preferences-> user code snippet-> lua

Parameter explanation:

Prefix: this parameter is a shortcut to using code snippets. For example, the log here will have IntelliSense by typing log when using it.

Body: this is the body of the code snippet. The code that needs to be set is placed here, and the line breaks between strings are separated by\ r\ nnewline characters. Note that if the value contains special characters, it needs to be escaped.

Multi-line statements are separated by.

1: this is the location of the cursor.

2: after using this parameter, the next position of the cursor will be another line. Press the tab key to switch quickly, and you can also have $3men.4meme 5.

Description: code snippet description, description when using IntelliSense

This is the end of this article on "the solution to vscode lua breakpoint failure". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.