Why do I receive a segmentation violation when I try to run a SimMechanics 2.1.1 (R13SP1) demo on Linux?

1 view (last 30 days)
Why do I receive a segmentation violation when I try to run a SimMechanics 2.1.1 (R13SP1) demo on Linux?
I am trying to simulate a SimMechanics model, such as the mech_dpen demo. When I start the simulation, I receive a segmentation violation.
-------------
Segmentation violation detected at Thu Oct 23 11:49:28 2003
-------------
Configuration:
MATLAB Version:6.5.1.199709 (R13) Service Pack 1
Operating System: Linux 2.4.20-64GB-SMP #1 SMP Thu Jul 10 17:28:06 UTC 2003 i686
Window System: The XFree86 Project, Inc (40300000), display :0.0
Current Visual:0x21 (class 4, depth 24)
Processor ID: x86 Family 6 Model 8 Stepping 6, GenuineIntel
Virtual Machine: Java 1.3.1 with Blackdown Java-Linux Team Java HotSpot(TM) Server VM
(mixed mode)
Register State:
eax = 00000084ebx = 421c5ef0
ecx = 00000001edx = 00000001
esi = 00000020edi = 4f7bfec0
ebp = bfff8518esp = bfff8490
eip = 420c6cd8flg = 00010206
Stack Trace:
[0] libjvm.so:Node::operator new(unsigned int)~(0x4f6e89b0, 0x41b75920 "¸]ÆOð÷¶A", 0x6f737365, 0x4f9b368e) + 36 bytes
[1] mechanical.mexglx:Machine::Machine(MachineKernel *)(0x4f8b2208, 0x41ca8bd0 "mech_dpen", 0xbfff8608, 0x4f9d04ea) + 72 bytes
[2] mechanical.mexglx:ModelRecord::compileGraph(PMMachineData_tag *)(0x4f017c00, 0x4f862490, 0xbfff8668, 0x4f9cec6a) + 1667 bytes
[3] mechanical.mexglx:ModelManager::compile(PMMachineData_tag *)(0x4f5c5d50, 0x4f862490, 695179, 0x4f98d2ae) + 74 bytes
[4] mechanical.mexglx:compileGraph(0x4f862490, 0x4f6de688, 0xbfff86d8, 0x4f9f2056) + 45 bytes
[5] mechanical.mexglx:mechCompile(void *)(0x4f862490, 0x4f7b4b08 "/home/rztit/matlab_crash_dump.15..", 0xbfff8728, 0x40b65960) + 135 bytes
[6] libmwsimulink.so:ExternalDomainEventFcn::execute(void *) const(0x41ba7908, 0x4f862490, 0x41bda5a8 "È:ºAÈ:ºA", 0x40b654b8) + 37 bytes

Accepted Answer

MathWorks Support Team
MathWorks Support Team on 27 Jun 2009
This has been verified as a bug in SimMechanics 2.1.1 (R13SP1) in the way that the Java Virtual Machine handles SimMechanics models on some installations of Linux.
Currently, to work around this issue, try starting MATLAB without the JVM enabled.
matlab -nojvm

More Answers (0)

Categories

Find more on Multibody Modeling in Help Center and File Exchange

Products


Release

R13SP1

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!