{"id":1638,"date":"2018-06-19T12:02:18","date_gmt":"2018-06-19T16:02:18","guid":{"rendered":"https:\/\/blogs.mathworks.com\/developer\/?p=1638"},"modified":"2018-06-20T08:26:43","modified_gmt":"2018-06-20T12:26:43","slug":"mex-debugging-vscode","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/developer\/2018\/06\/19\/mex-debugging-vscode\/","title":{"rendered":"MEX Debugging. Redefined."},"content":{"rendered":"

Folks, today I'd like to introduce a new guest blogger Martijn Aben. Martijn is a support engineer out of our Netherlands office who daydreams about MATLAB's connections to the external world. As part of that he as a great story to tell about how he has integrated with Microsoft's applauded VS Code IDE. Take it away Martijn!<\/em><\/p>\r\n

<\/em><\/p>\r\n

As a MathWorks Technical Support Engineer specializing, among other things, in the MATLAB \"external interfaces\" areas, I regularly work with MATLAB users having some difficulties<\/em> with their custom written MEX-files. Sometimes the MEX-files do not produce the expected result, and sometimes they completely crash MATLAB. This can happen because MEX-files are native libraries which can manipulate the native memory inside MATLAB and even the smallest memory corruption can easily lead to a whole application crashing. While we can\u2019t debug your MEX-file source code for you, this is not part of the support which we offer, we can help you with strategies to debug your code yourself. We can provide some hints and tips on what kind of issues to look out for, we can answer questions on the mxArray- and MEX APIs, and we can help you choose and setup your debug environment, which is what I\u2019d like to talk about in this post. <\/p>\r\n

Choosing your debug environment on Windows has historically been pretty simple. We supported the Microsoft Visual C++ compilers for creating MEX-files and if you used that compiler, Microsoft Visual Studio was the obvious choice for a debugger. In fact, getting started with this debugger is part of the actual in-product documentation<\/a>. <\/p>\r\n

However, in MATLAB R2015b we started to support the MinGW64 compiler which leverages the gdb<\/inline> debugger, and there are various different front-ends\/editors\/IDEs which can work with gdb<\/inline>. Immediately after the release of MATLAB R2015b, I wrote up a guide on how to debug using Eclipse, which my colleagues turned into a MATLAB Answer Article<\/a>. Today in this blog post we are looking into a different tool, which is one of my recent-favorite free development tools: Visual Studio Code<\/a> (VS Code). <\/p>\r\n

Visual Studio Code<\/h3>\r\n

When I first tried Visual Studio Code it was still the preview build. It looked like a nice and sleek code editor but I did not immediately recognize how powerful it can be when extensions are added. I recently rediscovered the tool and its extensibility when doing a little hobby IoT project, which showed me how powerful VS Code really has become. As a MathWorks employee and overall MATLAB fan, I then decided to see whether I could use it for debugging MEX-files as well. <\/p>\r\n

Now before we get to the actual setup and debugging, first a few things you need to know about VS Code. In particular, users of the full-fledged Visual Studio may be wondering how to create a Solution and add Projects to it since these do not exist in VS Code, at least not under those names. To create<\/em><\/b> something similar to a Project <\/em><\/b>you essentially Open<\/em><\/b> a Folder<\/em><\/b> and then organize things together in that Folder<\/em><\/b>. Want to open additional projects next to the one you already have open? Add<\/em><\/b> another Folder<\/em><\/b> to your Workspace<\/em><\/b>. Want to create something similar to a Solution<\/em><\/b> with multiple Projects<\/em><\/b>? Open multiple Folders<\/em><\/b> in your Workspace<\/em><\/b>, then Save<\/em><\/b> this Workspace<\/em><\/b>. Opening a solution has then become opening a workspace. <\/p>\r\n

Another important thing to note is that out-of-the-box VS Code is a powerful code editor for many languages but really only a debugger for Javascript and Typescript running in Node.js. For other languages and runtimes you will need to install the relevant extension(s). Since MATLAB MEX-files are written in C\/C++ this means we will need an extension, and that extension is aptly named \"C\/C++\". So let's get started by actually installing this extension. Fire up VS Code and head over to the Extensions section in VS Code: <\/p>\r\n

<\/p>\r\n

Find the C\/C++ Extension:<\/p>\r\n

<\/p>\r\n

And install it using that little green Install<\/inline> button, to fully complete the installation make sure to click the Reload<\/inline> option after the extension was downloaded. <\/p>\r\n

MEX-File Debugging in VS Code<\/h3>\r\n

Now that we have a VS Code installation which can debug C\/C++ code, let's see how we can configure it for the specific task of debugging MEX-files. We go to the Explorer<\/inline> section of VS Code and then use File<\/inline> -> Open Folder...<\/inline> to start a new Project<\/em><\/b>. In my example here I actually open the folder in which the source code of my MEX-file is located. After opening that folder, named Work<\/inline> in my case, and opening the source code of mymex.c<\/inline> in the editor, VS Code will look something like: <\/p>\r\n

<\/p>\r\n

First thing we notice is the #include \"mex.h\"<\/inline> statement being underlined and we also see some PROBLEMS<\/inline> being reported. You do not actually have to resolve these PROBLEMS<\/inline> to be able to debug most parts of your code but you may want to read up on these \"include issues\" in the VS Code documentation<\/a> and then create a c_cpp_properties.json <\/inline>with something like: <\/p>

\r\n{\r\n    \"configurations\": [\r\n        {\r\n            \"name\": \"Win32\",\r\n            \"includePath\": [\r\n                \"c:\/ProgramData\/MATLAB\/SupportPackages\/R2018a\/3P.instrset\/mingw_w64.instrset\/x86_64-w64-mingw32\/include\",\r\n                \"c:\/MATLAB\/R2018a\/extern\/include\",\r\n                \"${workspaceRoot}\"\r\n            ],\r\n            \"defines\": [\r\n                \"_DEBUG\",\r\n                \"UNICODE\",\r\n                \"_UNICODE\"\r\n            ],\r\n            \"intelliSenseMode\": \"msvc-x64\",\r\n            \"browse\": {\r\n                \"path\": [\r\n                    \"c:\/ProgramData\/MATLAB\/SupportPackages\/R2018a\/3P.instrset\/mingw_w64.instrset\/x86_64-w64-mingw32\/include\",\r\n                    \"c:\/MATLAB\/R2018a\/extern\/include\",\r\n                    \"${workspaceRoot}\"\r\n                ],\r\n                \"limitSymbolsToIncludedHeaders\": true,\r\n                \"databaseFilename\": \"\"\r\n            }\r\n        }\r\n    ],\r\n    \"version\": 3\r\n}\r\n<\/pre>
In which we tell VS Code where to find the MinGW64 headers as well as where to find the MATLAB headers. My MATLAB R2018a, which I am working with here, is installed in c:\\MATLAB\\R2018a<\/inline>, update your paths accordingly. My MinGW64 support package is installed in the default location so in most cases you should be able to re-use the location shown above. However, just in case you run into problems check the footnote at the end of this post to double check this location. <\/p>\r\n      
With VS Code all happy now, let's add a Debug configuration. We go to go to Debug<\/inline> -> Add Configuration\u2026<\/inline> and select C++ (GDB\/LLDB)<\/inline>: <\/p>\r\n      
<\/p>\r\n      
This will create a new  launch.json<\/inline> file for us and it should immediately show a menu to add new configurations. Alternatively you can use the Add Configuration\u2026<\/inline> button. Since it is faster\/easiest to attach to an already running MATLAB for debugging rather than launching a new one through the debugger, we choose to Add a C\/C++: (gdb) <\/inline> Attach<\/inline><\/b> configuration: <\/p>\r\n      
 <\/p>\r\n      
VS Code then automatically adds a new section to launch.json<\/inline>: <\/p>
\r\n{ \r\n    \"name\": \"(gdb) Attach\",\r\n    \"type\": \"cppdbg\",\r\n    \"request\": \"attach\",\r\n    \"program\": \"enter program name, for example ${workspaceRoot}\/a.exe\",\r\n    \"processId\": \"${command:pickProcess}\",\r\n    \"MIMode\": \"gdb\",\r\n    \"miDebuggerPath\": \"\/path\/to\/gdb\"\r\n}\r\n<\/pre>\r\n      
We need to update the program<\/inline> setting to point to MATLAB.exe from the bin\/win64<\/inline> directory of our MATLAB installation and miDebuggerPath <\/inline>to point to the gdb<\/inline> debugger from the MinGW64 Support Package. Also, the gdb<\/inline> debugger tends to stop on all first chance SIGSEGVs, so it actually stops on any thrown SIGSEGV even if that SIGSEGV is going to be caught and dealt with correctly. The JVM inside MATLAB throws these SIGSEGVs on purpose and then catches these as part of its JIT process and we do not want to stop in the debugger every time this happens. To tell the debugger to ignore these SIGSEGVs we add setupCommands <\/inline>which are essentially gdb<\/inline> commands which are automatically run when the debugger is started. All this combined then gives: <\/p>
\r\n{ \r\n    \"name\": \"(gdb) Attach\",\r\n    \"type\": \"cppdbg\",\r\n    \"request\": \"attach\",\r\n    \"program\": \"c:\/MATLAB\/R2018a\/bin\/win64\/MATLAB.exe\",\r\n    \"processId\": \"${command:pickProcess}\",\r\n    \"MIMode\": \"gdb\",\r\n    \"setupCommands\": [\r\n        {\r\n            \"text\": \"handle SIGSEGV nostop\"\r\n        },\r\n        {\r\n             \"text\": \"handle SIGSEGV noprint\"\r\n        }\r\n    ],\r\n    \"miDebuggerPath\": \"c:\/ProgramData\/MATLAB\/SupportPackages\/R2018a\/3P.instrset\/mingw_w64.instrset\/bin\/gdb.exe\"\r\n}\r\n<\/pre>\r\n      
From there I usually delete the (gdb) Launch <\/inline>configuration which had been added by default as well. That should complete the setup of our project, now we can get to the actual debugging. <\/p>\r\n      
Actual Debugging<\/h3>\r\n      
If you paid closed attention in the screenshots above, you could see that I had already compiled mymex.c<\/inline> into mymex.mexw64<\/inline>, I had prepared this earlier<\/em> in MATLAB with: <\/p>
mex -g<\/span> mymex.c<\/span>\r\n<\/pre>
Where the -g<\/inline> flag disabled optimizations and made sure symbolic information which we need for debugging was added. You will likewise need to build your mex files with this debug information using the -g<\/inline> flag. <\/p>\r\n      
So really all we need to do now is place a breakpoint somewhere in the code:<\/p>\r\n      
<\/p>\r\n      
Switch to the debug view <\/p>\r\n      
Make sure MATLAB is actually running<\/em> (we configured VS Code to attach<\/em> the debugger to an already running MATLAB after all) and we then hit the play button: <\/p>\r\n      
<\/p>\r\n      
Which shows a dialog with running processes where we then choose MATLAB:<\/p>\r\n      
 <\/p>\r\n      
VS Code should now be attached to MATLAB and we should see some lines like<\/p>
\r\n[New Thread 18404.0x473c]\r\n[New Thread 18404.0x3294]\r\n<\/pre>\r\n      
in the Debug Console<\/inline> which shows us that the debugger is definitely doing something<\/em> and is logging information about what MATLAB is doing. We can then switch to our MATLAB session and run the MEX-file: <\/p>
mymex([1 2 pi 21])\r\n<\/pre>
When we do that we will see VS Code will stop on our breakpoint, stepping (F10) a few lines we can then see:<\/p>\r\n      
<\/p>\r\n      
    \r\n         
    1. We were able to successfully obtain a pointer to the native input data and the first element had value 1<\/p>\r\n         
    2. The size of the input was indeed a 1x4 vector.<\/p>\r\n      <\/ol>\r\n      
    We can also step through our for<\/inline>-loop and see: <\/p>\r\n      
    <\/p>\r\n      
      \r\n         
      1. How i<\/inline> updates with each iteration, here we are at i = 3<\/inline>. <\/p>\r\n         
      2. Inspect certain elements in our array in the DEBUG CONSOLE<\/inline>. The screenshot shows that the fourth element in the input is indeed 21, just like we passed in from MATLAB. <\/p>\r\n      <\/ol>\r\n      
      To find out what else you can do, read the Debugging Documentation of VS Code<\/a>. <\/p>\r\n      
      Conclusion<\/h3>\r\n      
      I realize we did not actually debug and fix any bugs in any super advanced real-world MEX-files here today, but I did show you how you can get started on debugging MEX-files using one of my recent-favorite free development tools and I hope this has inspired you to give this workflow a try if you ever need to debug one of your MinGW64 MEX-files. Happy hunting for those bugs! <\/p>\r\n      
      Oh, and for you Linux users out there, while the story above is about MinGW64 and Windows, since VS Code is available for Linux as well, you can also apply this workflow on Linux to debug your GCC MEX-files. Obviously some of the paths will be somewhat different, but I am sure you can figure it out; let us know though if you have any further questions on that. <\/p>\r\n      
      Footnote<\/em><\/h3>\r\n      
        \r\n         
        While configuring VS Code we needed the location of the MinGW64 include directory as well as the location of the <\/em> gdb<\/inline><\/em> debugger. When MinGW64 is installed through the support package these locations may be somewhat hidden from you; also the exact locations may vary with different support package versions for different MATLAB releases. So how do you determine those locations? Well, <\/em> gdb.exe<\/inline><\/em> is typically found in the same directory as gcc\/g++ which is the actual compiler used for compilation, and you can easily see where the compiler is located if you add the verbose <\/em> -v<\/inline><\/em> flag when compiling your code: <\/em> mex -g -v mymex.c<\/inline><\/em>. In the verbose output, the last few lines show the literal calls that are being made to gcc\/g++. If you also want to find the include directory you go one directory up from gcc\/g++ and then into <\/em> x86_64-w64-mingw32<\/inline><\/em> where there will be a directory named <\/em> include<\/inline><\/em>.<\/em><\/p>\r\n      <\/ol>","protected":false},"excerpt":{"rendered":"
        \"\"<\/div>
        Folks, today I'd like to introduce a new guest blogger Martijn Aben. Martijn is a support engineer out of our Netherlands office who daydreams about MATLAB's connections to the external world. As... read more >><\/a><\/p>","protected":false},"author":90,"featured_media":1622,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[28,10],"tags":[],"_links":{"self":[{"href":"https:\/\/blogs.mathworks.com\/developer\/wp-json\/wp\/v2\/posts\/1638"}],"collection":[{"href":"https:\/\/blogs.mathworks.com\/developer\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.mathworks.com\/developer\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.mathworks.com\/developer\/wp-json\/wp\/v2\/users\/90"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.mathworks.com\/developer\/wp-json\/wp\/v2\/comments?post=1638"}],"version-history":[{"count":4,"href":"https:\/\/blogs.mathworks.com\/developer\/wp-json\/wp\/v2\/posts\/1638\/revisions"}],"predecessor-version":[{"id":1652,"href":"https:\/\/blogs.mathworks.com\/developer\/wp-json\/wp\/v2\/posts\/1638\/revisions\/1652"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.mathworks.com\/developer\/wp-json\/wp\/v2\/media\/1622"}],"wp:attachment":[{"href":"https:\/\/blogs.mathworks.com\/developer\/wp-json\/wp\/v2\/media?parent=1638"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.mathworks.com\/developer\/wp-json\/wp\/v2\/categories?post=1638"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.mathworks.com\/developer\/wp-json\/wp\/v2\/tags?post=1638"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}