Hi, thanks for the great matlab emacs, I have been using since R2011a all the
way to R2016a.
I’ve recently updated to Matlab R2016b, and I get a segfault, sometimes
accompanied with the message below (and sometimes not).
objc[761]: Class JavaLaunchHelper is implemented in both
/Applications/MA
Hi all,
I’ve been experiencing the same issue with Matlab R2016b on 10.10. This
issue occurs when launching R2016b from within any version of Emacs. As
Cumhur reported, all previous versions of Matlab seem to work fine. It
doesn’t matter how Matlab is launched from within Emacs; as such, this
i
I have had no luck.
It seems to have to do with some bug in the JAVA version bundled with
MATLAB. see this StackOverflow answer:
https://stackoverflow.com/questions/18794573/objc10012-class-javalaunchhelper-is-implemented-in-both-libinstrument-dyl
I spent quite some time trying to get MATLAB to w
in the past i had some issues with the matlab bundled java version under debian
wheezy, which i solved by using the native java version of my system. the bash
script to start matlab was:
#!/bin/bash
export MATLAB_JAVA=/usr/lib/jvm/java-7-openjdk-amd64/jre/
/usr/local/bin/matlab8 $1 $2
On Tue,
in the past i had some issues with the matlab bundled java version under debian
wheezy, which i solved by using the native java version of my system. the bash
script to start matlab was:
#!/bin/bash
export MATLAB_JAVA=/usr/lib/jvm/java-7-openjdk-amd64/jre/
/usr/local/bin/matlab8 $1 $2
On Tue,
in the past i had some issues with the matlab bundled java version under debian
wheezy, which i solved by using the native java version of my system. the bash
script to start matlab was:
#!/bin/bash
export MATLAB_JAVA=/usr/lib/jvm/java-7-openjdk-amd64/jre/
/usr/local/bin/matlab8 $1 $2
On Tue,
ail.com>>
Cc: Eric Greenwood mailto:eric.greenw...@nasa.gov>>,
matlab-emacs
mailto: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
in the past i had some issues with the mat
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 s
: 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
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 t
segfaults with matlab R2016b
on Mac OS 10.11.6 Emacs 25.1
still crashing with JAVA_VERSION="1.8.0_111"
$ export MATLAB_JAVA="/Library/Internet
Plug-Ins/JavaAppletPlugin.plugin/Contents/Home"
$ printenv MATLAB_JAVA
/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/
still crashing with JAVA_VERSION="1.8.0_111"
$ export MATLAB_JAVA="/Library/Internet
Plug-Ins/JavaAppletPlugin.plugin/Contents/Home"
$ printenv MATLAB_JAVA
/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home
$ /Applications/MATLAB_R2016b.app/bin/matlab -nodesktop
Java HotSpot(TM) 64-B
Hi Eric,
I'm glad to see that you're on this problem. I couldn't get any interest
from emacs-devel.
Please see below -- I'm running 2016a right now under emacs, and it mostly
behaves fine. Diff-ing the sys/java directories, I see no differences! Is
it possible that this is not a java issue? I
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 p
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
-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
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
2016 4:20 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
Hello,
Is max-lisp-eval-depth what you are looking for?
max-lisp-eval-depth is a variable defined in 'C source code
up all available memory.
>
> Eric
>
> From: Rhys Thomas [mailto:e.rhys.tho...@gmail.com]
> Sent: Sunday, December 18, 2016 4:20 AM
> To: matlab-emacs-discuss@lists.sourceforge.net
> Subject: Re: [Matlab-emacs-discuss] matlab-shell segfaults with matlab R2016b
> on Mac
:
>>
>> Hi Rhys,
>>
>> I am referring to the C stack size (the amount of memory allocated for both
>> the stack and variables of a running C program. In this case MATLAB as a
>> subprocess is being limited in how big it’s stack can be because its parent
>>
19 matches
Mail list logo