1. Make sure Visual Studio is your selected C compiler:
cc = mex.getCompilerConfigurations('C','Selected');
'Microsoft Visual C++ 2017 (C)'
2. Compile the source MEX file with the -g option, which builds the file with debugging symbols included. For example:
mex -g yprime.c
3. Start Visual Studio. Do not exit your MATLAB® session.
4. From the Visual Studio Debug menu, select Attach to Process.
5. In the Attach to Process dialog box, select the MATLAB process, and click Attach.
Ensure that the Attach to: parameter is set to Automatic: Native Code
Visual Studio loads data then displays an empty code pane.
6. Open the source file "yprime.c" by selecting File > Open > File. Locate "yprime.c" in the folder, "c:\work"
7. Set a breakpoint by right-clicking the desired line of code and following Breakpoint > Insert Breakpoint* *the context menu. It is often convenient to set a breakpoint at "mexFunction" to stop at the beginning of the gateway routine.
If you have not yet run the executable file, ignore any “!” icon that appears with the breakpoint next to the line of code.
Once you hit one of your breakpoints, you can make full use of any commands the debugger provides to examine variables, display memory, or inspect registers.
8. Open MATLAB and type:
9. If you select Debug > Continue, MATLAB displays:
2.0000 8.9685 4.0000 -1.0947
For more information on how to debug in the Visual Studio environment, see your Microsoft documentation.
Notes on Debugging
1. To avoid stepping into a MathWorks-provided function, use "Step Over" on lines that contain calls to MathWorks APIs.
2. To avoid stepping out into MathWorks code at the end of your custom function, use the "continue" (play button) when at the end of your function.
3. Do not enable "Access Violation" for handling exceptions when debugging MEX files. To avoid breaking at this exception, clear the check box for Win32 Exceptions. For Visual Studio 2015, look for the check box in Debug > Windows > Exception Settings.... If you are using a different version of Visual Studio, refer to the corresponding Microsoft documentation.
Binary MEX files built with the -g option do not execute on other computers because they rely on files that are not distributed with MATLAB. For more information on isolating problems with MEX files, see Troubleshoot MEX Files.