[25583] in Athena Bugs
Re: sun4 9.2.28: matlab
daemon@ATHENA.MIT.EDU (Daniel Jamous)
Wed Apr 7 10:14:48 2004
Message-Id: <5.1.0.14.2.20040407100934.00b9cf78@hesiod>
Date: Wed, 07 Apr 2004 10:14:34 -0400
To: Asanka C Herath <asanka@mit.edu>, Alex T Prengel <alexp@mit.edu>
From: Daniel Jamous <jamous@mit.edu>
In-Reply-To: <Pine.GSO.4.55L.0404061754540.10578@no-knife.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
cc: bugs@mit.edu
Errors-To: bugs-bounces@mit.edu
Hi,
This is a tricky one.
Not sure we'll be able to find a workaround. In the meantime, I found this
on the MathWorks documentation, which might be useful.
"Understanding MEX-File Problems" at:
http://www.mathworks.com/access/helpdesk/help/techdoc/matlab_external/ch2_c_19.html#27314
Daniel
At 06:06 PM 4/6/2004 -0400, Asanka C Herath wrote:
> > There's no easy way around this, other than unwrapping Matlab which we
> > don't want to do. If it's important that you be able to run this so
> > you can debug someone's problem, I can temporarily make it possible
> > for you to access an unwrapped copy (for a few hours or so).
>
>This actually came up as an OLC question. The user wants to debug MEX
>files. We suggested a workaround for him which is to set MATLAB_DEBUG by
>hand and attach the debugger to the running Matlab process (which
>"works-for-me" under Solaris, but has problems on Linux).
>
>Since unwrapping the binary doesn't seem to be an option for general
>users, I think a good workaround should be documented and made available
>to users. Maybe the startup script could mention it too (if they try to
>use -D). People who work with MEX would need it.
>
>-- Asanka
