surroundings:

OS：win10

slickedit：V23

mingw：mingw—x86-64-7.3.1

 

The main introduction here is how to use slickedit and mingw to compile the code, so the steps to install slickedit and mingw are omitted. I installed qt5.12.6 with mingw. After installing mingw, you need to add the path to the system.

Step 1: Right-click This PC--->Proterties--->Advanced system settings--->Advanced--->Environment Variables...--->System variables--->Path---> on the desktop Edit--->New--->Add the path of mingw, my path is C:\Qt\Qt5.12.6\Tools\mingw730_64\bin

 

After setting the environment variables, we use slickedit to build a project. I have created a study project here (note whether a makefile needs to be selected according to your actual needs when creating the project, I am just a simple demonstration here, no make is selected). As shown below:

Step 2: Build--->GNU C Options...

Step 3: Select Compile in the pop-up GNU C Options dialog box, and then select Compiple belowr: Select the path where g++ of mingw is located.

Step 4: Select Link in the GNU C Options dialog box, and then select the path where mingw's g++ is located in the following Linker.

Step 5: Select Compile--->Build--->Execute, etc. in Build.

The operation result is shown in the following figure:

 

Next, a brief introduction to the settings when debugging code.

Step 1: Select Debugger Options... in the Debug drop-down menu. Note that I have already indicated that the shortcut key for setting a breakpoint with the red line is F9. As shown below:

Step 2: Select Debugging--->Configurations in the pop-up window, and then click the plus sign in the upper right corner to select mingw's gdb. As shown below:

Step 3: Set the code breakpoint, click the line where the code needs to be set, and press F9. (The red dot in the box on line 9 is the breakpoint)

Step 4: Select Attach Debugger in Debug, and then select Debug Executable (GDB), as shown in the following figure:

Note: There are a variety of debugging methods in Attach Debugger, including remote debugging, debugging already running programs, etc., you can also use coredump files, etc.

Step 5: Select the generated execution file and source code file directory in the pop-up window, as shown in the following figure:

Step 6: I clicked Run directly here, and the program started to execute and stayed at line 9 of the code, as follows:

At this time, look at the Debug pull-down menu, F5, F11, F10, and other debugging shortcut keys can be used. For example, pressing F10 will continue to print 10. Note: I used Visual Studio default for slickedit simulation.

If you are using other programming languages ​​such as python, you may need additional settings in the established project, specifically I did not try. Right-click on the created project and select Project Properties... from the pop-up menu as shown below:

In the dialog box that pops up, GDB (GNU Debugger) is used by default. For languages ​​such as Python, additional settings may be required here. Here is just a reminder.

Note: The slickedit I use is emulated by Visual Studio default. This will be selected when installing slickedit. You can also select yourself through Tools--->Quick Start Configuration...--->Emulation---> Like and get used to simulation.