Hi all,

We identified that MATLAB on the MAC platform can be reproduced with a similar 
output to what has been noted here with:

matlab -nodisplay -nojvm

In this case, the line:

matlab.internal.supportPackages.addInstalledSupportPackagesToPath

in matlabrc.m is the culprit.  If you don’t have support packages installed, 
and if you have write permission to your MATLAB install, you can probably 
comment out this line to have MALTAB get past this step.

I haven’t tested this (I don’t have a Mac) and the developer who found this 
isn’t an Emacs person, so I’m speculating about this workaround.

Eric

From: Peter Mao [mailto:peter....@gmail.com]
Sent: Monday, November 14, 2016 11:18 AM
To: matlab-emacs-discuss@lists.sourceforge.net
Subject: Re: [Matlab-emacs-discuss] matlab-shell segfaults with matlab R2016b 
on Mac OS 10.11.6 Emacs 25.1

Further evidence (I hope this helps someone solve the problem):
1. 2016b works in NONE of the emacs terminals: shell, term or e-shell.
2. 2016b works fine (even with -nodesktop) from Xquartz's xterm or OSX's 
terminal
3. 2016a works fine in emacs
4. Running diff on the java directories (where the potentially offending files 
reside) shows NO difference between 2016a and 2016b!
    $ diff -ur /Applications/MATLAB_R2016b.app/sys/java 
/Applications/MATLAB_R2016a.app/sys/java
This might not be a Java issue.

On Thu, Nov 10, 2016 at 7:37 PM, Peter Mao 
<peter....@gmail.com<mailto:peter....@gmail.com>> wrote:
Yes, I'm seeing this problem, too.  Mathworks won't touch it, as it does seem 
to be a real third party issue with Emacs.
I'm having the problem with OSX 10.12 and Emacs 25.1.1, although it was also 
present with my previous emacs (24.5?).
I checked the environment variables, and the only thing I see significantly 
different is that emacs shell reports as TERM=dumb, while the Xquartz one is 
TERM=xterm and apple's terminal is TERM=xterm-256color.
In all cases, the actual shell is /bin/bash.  I'm guessing this has something 
to do with how emacs is setting up the shell, but I can't figure out what the 
issue is, exactly.  May be time to cross post to emacs developers.
Peter

------------------------------------------------------------------------------
_______________________________________________
Matlab-emacs-discuss mailing list
Matlab-emacs-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss

Reply via email to