Hello Jesse,
I understand that you are facing issues after reattaching the Visual Studio Debugger. To address this issue, please follow this workaround :
1. Deattach Visual Studio Debugger from Matlab
2. Clear mex or clear [Sfcn-Name].mexw32
3. Attach Visual Studio Debugger to Matlab
If the issue persists, then it is advisable to check the Visual Studio debugger setup. If the Visual Studio debugger does indeed not stop at breakpoints, then there are some quirks with attaching Visual Studio (2015, 2017, 2019, or 2022) as a debugger for external code in Simulink. Typically things need to be done in a certain sequence for it to work right as listed below.
Kindly, see also the "Debugging C MEX S-Functions Using the Microsoft Visual C++ .NET Environment" example for details:
1. PDB files are required for Visual Studio to debug an S-function since they contain the symbols related to that source file. It should be ensured that the MEX files for the S-function are generated using the right compiler i.e., Visual Studio in this case. The compiler being used can be checked by entering the following command:
>> mex -setup C
2. Next, ensure you have disabled Simulation Target > Enable Custom Code Analysis in the configuration parameters of your Simulink model.3. In MATLAB R2022a and earlier, make sure that the execution of the below command returns 1 (true):
>> Simulink.CustomCode.debugSymbols('on')
In MATLAB R2022b and newer, this option is always turned on.4. Next, issue the following command at the MATLAB Command Window to delete any existing MEX files and cache(s):
>> clear mex
5. Attach the Visual Studio debugger to the MATLAB.exe process
6. Add a breakpoint to the source code in Visual Studio. At this stage, Visual Studio will still say the breakpoint will not be hit. This is expected.
7. Return to Simulink and update the model (Ctrl+D)
8. Now, the breakpoint will light up in Visual Studio and function as normal. Breakpoints you place will be hit as you simulate the model.
