SOLUTION: I found a solution from a separate forum; I am posting here in case anyone has a similar issue. Essentially, the external solver depends on bash environment variables stored in my home .bash_profile and other locations. These variables are not accessible to MATLAB. Therefore, in my main MATLAB script, I added a bunch of "setenv()" commands to set these variables within the script itself. This makes the variables accessible to the external solver so that it functions properly.
System Command Gives Segmentation Fault?
7 visualizaciones (últimos 30 días)
Mostrar comentarios más antiguos
Hello! I am using an external solver to run simulations. I am trying to call the external solver with system(cmd) from a MATLAB script. The cmd itself runs fine with no problems from the Terminal (I'm running on OSX). However, every time the MATLAB script runs, the status is 139 - Segmentation Fault. Does anyone know why this might be happening?
2 comentarios
Walter Roberson
el 20 de En. de 2017
Another approach might have been to use something like,
system('source ~/.bash_profile; rest of command')
Respuestas (1)
Walter Roberson
el 20 de En. de 2017
It is a DYLD_DYNAMIC_PATH problem. MATLAB puts a dynamic path environment variable that either is missing a directory the executable needs or else puts a directory in priority that contains an incompatible dynamic path.
At the terminal window examine the environment variable. Then in your MATLAB program before calling system, use setenv() to set the environment variable to that same thing.
0 comentarios
Ver también
Categorías
Más información sobre Environment and Settings en Help Center y File Exchange.
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!