Matlab crash (segmentation fault)

My code has crashed a couple of times over the last weeks. I am using some mex functions of mine that I believe are safe, as they never crashed in several years, but you never know... The crash dump file is not very helpful (see below). Normally it would tell which file/library is involved in the crash, but it this case I only have

Stack Trace (from fault):
[  0] 0x0000000000000001                                   <unknown-module>+00000000

Is there any way to know whether this comes from my mex files or from Matlab itself?

Thanks a lot

(full crash dump file below)

------------------------------------------------------------------------
       Segmentation violation detected at Wed Jun  7 10:15:42 2017
------------------------------------------------------------------------

Configuration:
  Crash Decoding      : Disabled - No sandbox or build area path
  Crash Mode          : continue (default)
  Current Graphics Driver: NVIDIA Corporation GeForce GTX 670/PCIe/SSE2 Version 4.5.0 NVIDIA 375.66
  Current Visual      : 0x21 (class 4, depth 24)
  Default Encoding    : UTF-8
  Deployed            : false
  GNU C Library       : 2.23 stable
  Host Name           : inm-mint-18
  MATLAB Architecture : glnxa64
  MATLAB Entitlement ID: 1208320
  MATLAB Root         : /usr/local/MATLAB/R2016b
  MATLAB Version      : 9.1.0.441655 (R2016b)
  OpenGL              : hardware
  Operating System    : Linux 4.8.0-52-generic #55~16.04.1-Ubuntu SMP Fri Apr 28 14:36:29 UTC 2017 x86_64
  Processor ID        : x86 Family 6 Model 58 Stepping 9, GenuineIntel
  Virtual Machine     : Java 1.7.0_60-b19 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
  Window System       : The X.Org Foundation (11804000), display :0

Fault Count: 1

Abnormal termination:
Segmentation violation

Register State (from fault):
  RAX = 0000000000000001  RBX = 00007f7b253d65e0
  RCX = 0000000000000001  RDX = 00007f7a8bff5ba0
  RSP = 00007f7b437e5658  RBP = 0000000000000002
  RSI = 0000000000000001  RDI = 00007f7b253d65e0

     R8 = 0000000000000000   R9 = 0000000000000000
    R10 = 00007f7b2501a370  R11 = 00007f7a9da618b0
    R12 = 0000000000000008  R13 = 0000000000000002
    R14 = 0000000000000004  R15 = 0000000000000002

    RIP = 0000000000000001  EFL = 0000000000010202

     CS = 0033   FS = 0000   GS = 0000

Stack Trace (from fault):
[  0] 0x0000000000000001                                   <unknown-module>+00000000

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.

[Adam]

Did you do what it suggests and send it to Mathworks technical support? There's not much we in a user forum can do with a segmentation dump printout.

[Alexandre]

Hi Adam,

No I haven't sent it to tech support but I will. I am aware that a crash dump printout isn't very helpful but I just found it curious it says "unknown-module"

Answer 1

[Philip Borghesani]

An empty stack is usually caused by a call to a function pointer that is NULL from c/c++. It could also be due to calling a virtual function on a null object or by a function that corrupts the stack before returning. If your mex files are not likely to do this type of thing I would think about what updates you have installed on your computer recently, especially graphics drivers, and possibly try running with software opengl to see if the problem goes away. Without some reproduction steps a support call won't be very helpful in this situation ether.

Answer 2

[xing huang]

Hello, have you solved this problem?