Re: Debugging octave mex files

[Ben Abbott]

On Nov 28, 2011, at 4:53 PM, Trigui, Hafedh (OTT) wrote:

>   -----Original Message-----
> From: address@hidden [mailto:address@hidden On Behalf Of Jordi Gutiérrez 
> Hermoso
> Sent: Monday, November 28, 2011 4:45 PM
> To: Trigui, Hafedh (OTT)
> Cc: address@hidden
> Subject: Re: Debugging octave mex files
> 
>> On 28 November 2011 16:30, Trigui, Hafedh (OTT) <address@hidden> wrote:
>>> I am trying to debug mex files, generated by Microsoft Visual Studio 
>>> 2005, under octave-3.3.4 following the link 
>>> http://www.mathworks.com/help/techdoc/matlab_external/f32489.html?
>>> but the cursor never stopped at the breakpoint. Also, mex -g 
>>> myfunction.c resulted in myfunction.mex rather than myfunction.mexw32.
>> 
>> What does this question have to do with Octave? You produced a mex file with 
>> Matlab's mex binary, which is not something Octave can use at all. You would 
>> need to recompile your code with mkoctfile --mex if you want to produce a 
>> mex file for Octave. I am also not sure about using that compiler. How are 
>> you making Octave a part of this?
>> 
>> By the way, where did you get that version of Octave? Did you mean 3.4.3? 
>> Did you compile it yourself?
>> 
>>> What is the equivalent of such debugging in Octave?
>> 
>> oct files, but they use a different API than mex files (for backwards 
>> compatibility, Octave also provides a C++ API to mex files). They can be 
>> debugged like any other
>> 
>> ----------------------------------------------
>>> This e-mail from Ultra Electronics and any attachments to it are 
>>> confidential to the intended recipient and may also be privileged. If 
>>> you have received it in error please notify the sender and delete it 
>>> from your system. If you are not the intended recipient you must not 
>>> copy it or use it for any purpose nor disclose or distribute its contents 
>>> to any other person.
>> 
>> Am I the intended recipient? I'm not sure. I hope I am. If not, I can erase 
>> your email, if you wish.
>> 
>> - Jordi G. H.
> 
> I wrote the mexFunction and other C++ functions in visual studio 2005 and 
> also used the VS2005 compiler and linker. The use of octave is restricted to 
> pass variables and read outputs of mex files. 
> Everything run perfectly with octave 3.2.4 (sorry for the typo in my previous 
> email).
> 
> Since now I am moving in the direction of complicating my C++ code, I started 
> to think about debugging and ideally using VS2005 (very nice GUI, line by 
> line debug, variables watch...).
> 
> Do you or anyone else has a good idea on how to debug mex files?
> 
> Thanks 
> Hafedh 

If your version of Octave was built with VS2005, then what you want to do may 
be possible.

Can you tells us where you obtained (downloaded) Octave?

Ben