Re: [Matlab-emacs-discuss] matlab-shell segfaults with matlab R2016b on Mac OS 10.11.6 Emacs 25.1

2017-03-10 Thread Cumhur Erkut 
 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>   ... 23 more
> 
> 
> Bus error detected at Tue Dec 20 17:15:38 2016
> 
> 
> Configuration:
>  Crash Decoding  : Disabled - No sandbox or build area path
>  Crash Mode  : continue (default)
>  Current Graphics Driver: Unknown hardware 
>  Current Visual  : Quartz
>  Default Encoding: ISO-8859-1
>  Deployed: false
>  Host Name   : h304.aau1x-3.klient.sydhavn2.site.aau.dk
>  MATLAB Architecture : maci64
>  MATLAB Entitlement ID: 3623390
>  MATLAB Root : /Applications/MATLAB_R2017a.app
>  MATLAB Version  : 9.2.0.494151 (R2017a) Prerelease
>  OpenGL  : hardware
>  Operating System: Darwin 16.3.0 Darwin Kernel Version 16.3.0: Thu Nov 17 
> 20:23:58 PST 2016; root:xnu-3789.31.2~1/RELEASE_X86_64 x86_64
>  Processor ID: x86 Family 6 Model 70 Stepping 1, GenuineIntel
>  Virtual Machine : Java 1.7.0_75-b13 with Oracle Corporation Java 
> HotSpot(TM) 64-Bit Server VM mixed mode
>  Window System   : Quartz
> 
> Fault Count: 1
> 
> 
> Abnormal termination:
> Bus error
> 
> Register State (from fault):
>  RAX = 7b884338  RBX = 0003
>  RCX =   RDX = 00011f167ac0
>  RSP = 0001167e6dd8  RBP = 7b8840f0
>  RSI = 000107c7be7a  RDI = 7b8840c0
> 
>   R8 = 0001167e6e08   R9 = 7fb229087a00
>  R10 = 7b8840e0  R11 = 00010e33ab4a
>  R12 =   R13 = 
>  R14 = 7fb22b4df080  R15 = 7b884180
> 
>  RIP =   RFL = 00010c7a0ea7
> 
>   CS = 7b884100   FS = 000107bb1bdf   GS = 
> 
> Stack Trace (from fault):
> [  0] 0x0001079e3714   
> bin/maci64/libmwfl.dylib+00034580 
> _ZN2fl4diag15stacktrace_base7captureERKNS0_14thread_contextEm+0052
> [  1] 0x0001079e70ca   
> bin/maci64/libmwfl.dylib+00049354 _ZN2fl4test17terminate_handledEv+0810
> [  2] 0x0001079e6b39   
> bin/maci64/libmwfl.dylib+00047929 
> _ZN2fl4diag13terminate_logEPKcPK17__darwin_ucontext+0185
> [  3] 0x00010ac2d6c1  
> bin/maci64/libmwmcr.dylib+00435905 
> _Z19mnPrintErrorMessageRKNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIc+2081
> [  4] 0x00010ac2d010  
> bin/maci64/libmwmcr.dylib+00434192 
> _Z19mnPrintErrorMessageRKNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIc+0368
> [  5] 0x00010ac2ba0a  
> bin/maci64/libmwmcr.dylib+00428554 mnFatalSignalHandler+0154
> [  6] 0x7fffb4037bba   
> /usr/lib/system/libsystem_platform.dylib+00011194 _sigtramp+0026
> [  7] 0x0020   
> +
> [  8] 0x000107bb1bdf 
> bin/maci64/libmx.dylib+00043999 
> _ZN6matrix6detail10noninlined12mx_array_api31try_nonrecursive_mxDestroyArrayEP11mxArray_tag+0015
> [  9] 0x00010e33af8d 
> bin/maci64/libmwlxetypes.dylib+00098189 
> _ZN9MathWorks3lxe6xvalueC1ENSt3__110unique_ptrI11mxArray_tagN6matrix6detail17mxDestroy_deleterEEE+0077
> [ 10] 0x7b884230   
> +
> [ 11] 0x7b884198   
> +
> 
> 
> If this problem is reproducible, please submit a Service Request via:
>http://www.mathworks.com/support/contact_us/
> 
> A technical support engineer might contact you with further information.
> 
> Thank you for your help.** This crash report has been saved to disk as 
> /Users/cerkut/matlab_crash_dump.52230-1 **
> 
> MATLAB is exiting because of fatal error
> 
> M-Shell killed: 9
> ——
> 
> 
>> On 19 Dec 2016, at 15.02, Eric Ludlam <eric.lud...@mathworks.com> wrote:
>> 
>> 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 
>> (Emacs) has setup limits for that subprocess.
>> 
>> This can be a useful thing to do if you don’t always trust a subprocess, 
>> since it will prevent the subprocess from accidentally (or perhaps 
>> purposefully) locking up your computer by using up all available memory.
>> 
>> Eric
>> 
&g

Re: [Matlab-emacs-discuss] matlab-shell segfaults with matlab R2016b on Mac OS 10.11.6 Emacs 25.1

2016-12-18 Thread Rhys Thomas 

Hello,

Is max-lisp-eval-depth what you are looking for?

max-lisp-eval-depth is a variable defined in ‘C source code’.
Its value is 800

  This variable may be risky if used as a file-local variable.

Documentation:
Limit on depth in ‘eval’, ‘apply’ and ‘funcall’ before error.

This limit serves to catch infinite recursions for you before they cause
actual stack overflow in C, which would be fatal for Emacs.
You can safely make it considerably larger than its default value,
if that proves inconveniently small.  However, if you increase it too far,
Emacs could overflow the real C stack, and crash.


Regards,

Rhys

On 14/12/16 16:46, Eric Ludlam wrote:


Hello again,

I’ve been watching progress in development around this 
Mac/Emacs/MATLAB issue.   They have identified that the reason MATLAB 
is crashing in Emacs, but not on the command line is because Emacs is 
setting the stack size.  A way to reproduce outside of Emacs is as 
follows:


ulimit -s 8515

matlab

Stacks limited to sizes of 8512 or more works fine for them.

I looked into stack size within emacs, and saw several references to 
increasing the stack size to 8519 in Emacs to work around a bug I’m 
not familiar with, but not to a way to increase the stack size of 
sub-processes.


Any Emacs hackers on this list familiar with updating stack size for 
sub-processes in Emacs as a way to work around this problem?


Thanks

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



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot


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


--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Matlab-emacs-discuss mailing list
Matlab-emacs-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss

Re: [Matlab-emacs-discuss] matlab-shell segfaults with matlab R2016b on Mac OS 10.11.6 Emacs 25.1

2016-11-18 Thread Peter Mao 
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  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

Re: [Matlab-emacs-discuss] matlab-shell segfaults with matlab R2016b on Mac OS 10.11.6 Emacs 25.1

2016-11-01 Thread Fritz 
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, Nov 1, 2016 at 4:11 PM, Deepak Cherian 
> wrote:
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 work with an updated JDK, but 
that just caused other troubles (crashes).

I've gone back to 2016a which works fine.

Deepak


Deepak

On 28 October 2016 at 17:01, Greenwood, Eric (LARC-D314) 
> wrote:
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
isn’t really a matlab-emacs mode issue, but I’m hopeful someone else will
have found a solution!

Best Regards,
Eric Greenwood

-Original Message-

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/MATLAB_R2016b.app/sys/java/jre/maci64/jre/bin/java and
/Applications/MATLAB_R2016b.app/sys/java/jre/maci64/jre/lib/jli/libjli.dyli
b. One of the two will be used. Which one is undefined.

M-Shell segmentation fault: 11

I can launch Matlab R2016b fine from the command line.

Does anybody else get this? Any hints to avoid? ATM, I am keeping both
R2016a (works with emacs matlab) and (works as a stand alone).

Best wishes — Cumhur

--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
___
Matlab-emacs-discuss mailing list
Matlab-emacs-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss


--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Matlab-emacs-discuss mailing list
Matlab-emacs-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss


--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Matlab-emacs-discuss mailing list
Matlab-emacs-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss

Re: [Matlab-emacs-discuss] matlab-shell segfaults with matlab R2016b on Mac OS 10.11.6 Emacs 25.1

2016-11-01 Thread Fritz 
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, Nov 1, 2016 at 4:11 PM, Deepak Cherian 
> wrote:
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 work with an updated JDK, but 
that just caused other troubles (crashes).

I've gone back to 2016a which works fine.

Deepak


Deepak

On 28 October 2016 at 17:01, Greenwood, Eric (LARC-D314) 
> wrote:
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
isn’t really a matlab-emacs mode issue, but I’m hopeful someone else will
have found a solution!

Best Regards,
Eric Greenwood

-Original Message-

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/MATLAB_R2016b.app/sys/java/jre/maci64/jre/bin/java and
/Applications/MATLAB_R2016b.app/sys/java/jre/maci64/jre/lib/jli/libjli.dyli
b. One of the two will be used. Which one is undefined.

M-Shell segmentation fault: 11

I can launch Matlab R2016b fine from the command line.

Does anybody else get this? Any hints to avoid? ATM, I am keeping both
R2016a (works with emacs matlab) and (works as a stand alone).

Best wishes — Cumhur

--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
___
Matlab-emacs-discuss mailing list
Matlab-emacs-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss


--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Matlab-emacs-discuss mailing list
Matlab-emacs-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss


--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Matlab-emacs-discuss mailing list
Matlab-emacs-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss

Re: [Matlab-emacs-discuss] matlab-shell segfaults with matlab R2016b on Mac OS 10.11.6 Emacs 25.1

2016-11-01 Thread Fritz 
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, Nov 1, 2016 at 4:11 PM, Deepak Cherian 
> wrote:
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 work with an updated JDK, but 
that just caused other troubles (crashes).

I've gone back to 2016a which works fine.

Deepak


Deepak

On 28 October 2016 at 17:01, Greenwood, Eric (LARC-D314) 
> wrote:
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
isn’t really a matlab-emacs mode issue, but I’m hopeful someone else will
have found a solution!

Best Regards,
Eric Greenwood

-Original Message-

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/MATLAB_R2016b.app/sys/java/jre/maci64/jre/bin/java and
/Applications/MATLAB_R2016b.app/sys/java/jre/maci64/jre/lib/jli/libjli.dyli
b. One of the two will be used. Which one is undefined.

M-Shell segmentation fault: 11

I can launch Matlab R2016b fine from the command line.

Does anybody else get this? Any hints to avoid? ATM, I am keeping both
R2016a (works with emacs matlab) and (works as a stand alone).

Best wishes — Cumhur

--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
___
Matlab-emacs-discuss mailing list
Matlab-emacs-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss


--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Matlab-emacs-discuss mailing list
Matlab-emacs-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss


--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Matlab-emacs-discuss mailing list
Matlab-emacs-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss

Re: [Matlab-emacs-discuss] matlab-shell segfaults with matlab R2016b on Mac OS 10.11.6 Emacs 25.1

2016-10-28 Thread Greenwood, Eric (LARC-D314) 
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
isn’t really a matlab-emacs mode issue, but I’m hopeful someone else will
have found a solution!

Best Regards,
Eric Greenwood

-Original Message-

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/MATLAB_R2016b.app/sys/java/jre/maci64/jre/bin/java and
/Applications/MATLAB_R2016b.app/sys/java/jre/maci64/jre/lib/jli/libjli.dyli
b. One of the two will be used. Which one is undefined.

M-Shell segmentation fault: 11

I can launch Matlab R2016b fine from the command line.

Does anybody else get this? Any hints to avoid? ATM, I am keeping both
R2016a (works with emacs matlab) and (works as a stand alone).

Best wishes — Cumhur

--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
___
Matlab-emacs-discuss mailing list
Matlab-emacs-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss