Why does matlab command line die with Ctrl+C in Linux (matlab -nodesktop -nosplash)?

2 visualizaciones (últimos 30 días)
When I run Matlab on our Linux machine and type Control+C to interrupt Matlab execution, the Matlab terminal itself dies and returns me to the shell command line. I confirmed that the parent Matlab process is in fact still running so it appears that just the Matlab command line has died and not the parent Matlab process.
I also confirmed that this does not occur when using the full Matlab GUI. The GUI accepts Ctrl+C interrupts normally, interrupting Matlab code execution but not affecting the Matlab instance in any other way.
The behavior is also different from a suspend signal (Ctrl+Z) which prints "Suspended" to the command line and which can be revived using the "fg" command. As far as I know I am unable to revive the Matlab command line in any way and the parent process has to be killed manually with a "kill" command from the terminal.
Note: I have not seen this behavior on other Linux systems, but am at a loss of where/what to look at. The program gives no diagnostic information when it dies/returns to the shell command line. The Matlab command line ">>" simply becomes the shell command line.
Other system information:
OS: Red Hat Enterprise Linux 6
Matlab Version: 8.5.0.197613 (R2015a)
Matlab start command (run in tcsh): "matlab -nodesktop -nosplash"
Thanks in advance for any help!
Chris

Respuestas (0)

Categorías

Más información sobre Application Deployment en Help Center y File Exchange.

Productos

Community Treasure Hunt

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

Start Hunting!

Translated by