[25578] in Athena Bugs
Re: sun4 9.2.28: matlab
daemon@ATHENA.MIT.EDU (Asanka C Herath)
Tue Apr 6 18:07:05 2004
Date: Tue, 6 Apr 2004 18:06:42 -0400 (EDT)
From: Asanka C Herath <asanka@mit.edu>
To: Alex T Prengel <alexp@mit.edu>
In-Reply-To: <200404022304.i32N4rPt025769@dit.mit.edu>
Message-ID: <Pine.GSO.4.55L.0404061754540.10578@no-knife.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: jamous@mit.edu
cc: bugs@mit.edu
Errors-To: bugs-bounces@mit.edu
> 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
