User`s guide

R2010b
12-24
These types of programming errors are sometimes difficult to track down. Segmentation
violations do not always occur at the same point as the logical errors that cause them.
If a program writes data to an unintended section of memory, an error might not occur
until the program reads and interprets the corrupted data. Consequently, a segmentation
violation can occur after the MEX-file finishes executing.
One cause of memory corruption is to pass a null pointer to a function. To check for this
condition, add code in your MEX-file to check for invalid arguments to MEX Library and
MX Matrix Library API functions.
To troubleshoot problems of this nature, run MATLAB within a debugging environment.
For more information, see Debugging C/C++ Language MEX-Files or Debugging Fortran
Source MEX-Files.
MEX Function -inline Option Removed
Function Option Name What Happens When you use
the Option?
Compatibility Considerations
mex -inline option Errors Remove all existing
instances of -inline in
build scripts.
New Support for Features in Microsoft .NET Framework
MATLAB supports:
• Using .NET Delegates in MATLAB.
• Accessing Microsoft Office Applications with .NET.
• Using System.Nullable, described in How MATLAB Handles System.Nullable.
• Calling constructors or NET.invokeGenericMethod with ref or out type arguments.
• Calling methods with default arguments (System.Reflection.Missing.Value is
supported.)
New COM Data Type Support
Support for the following COM data type has been added. See Handling COM Data in
MATLAB Software for a description of supported data types.