Thread Subject: Efficient debugging of mex-files

Hello,

in the devolping process of C mex-files (both for MATLAB and Simulink)
the debugging process as described in Tech-Notes 1605 and 1819 is very
time-consuming.

I have always to load the dll, set MATLAB as application, load the
source file and start MATLAB to debug my functions. Is there a way to
accelerate this process? I am using Visual C 6.0 and Visual C .net.

Thank you

Michael

"Michael Salloker" <michael.NOSPAMsalloker@fh-joanneum.at> wrote in message
news:cp4593$t20$1@newsreader1.utanet.at...
> Hello,
>
> in the devolping process of C mex-files (both for MATLAB and Simulink)
> the debugging process as described in Tech-Notes 1605 and 1819 is very
> time-consuming.
>
> I have always to load the dll, set MATLAB as application, load the
> source file and start MATLAB to debug my functions. Is there a way to
> accelerate this process? I am using Visual C 6.0 and Visual C .net.
>
> Thank you
>
> Michael

I use the method described in the MexWizard package on the file exchange.
Maybe it will work for you.
-Aj

Michael Salloker wrote:
>
>
> Hello,
>
> in the devolping process of C mex-files (both for MATLAB and
> Simulink)
> the debugging process as described in Tech-Notes 1605 and 1819 is
> very
> time-consuming.
>
> I have always to load the dll, set MATLAB as application, load the
> source file and start MATLAB to debug my functions. Is there a way
> to
> accelerate this process? I am using Visual C 6.0 and Visual C .net.
>
> Thank you
>
> Michael
>

Well,

Personally after mexing with -g, I wrote a little mfile
initializating the dll, says test_mex.m where I put all my constant
,etc .. before calling the mex dll.

Then, in the debug setting of VC6.0, where you must locate the
matlab.exe, I also put theses following argurment in the parameter
fields

-minimize -nosplash -nodesktop -r test_mex

Then, I presse F5 in VC, matlab is automatically lunched, the
test_program launch the dll and it stop where I put the breakpoints.

Hope to help you.

Sébastien