Killing a (mex) Function When It Doesn't Respond to Ctrl-C or Ctrl-Break Under WIN64

조회 수: 24(최근 30일)
Is there a way to kill a (mex) function running in MATLAB and which doesn't respond to Ctrl-C or CTrl-Break, other than by killing the whole MATLAB process (session)? To be concrete, assume R2014A WIN 64.

채택된 답변

Jan 2015년 6월 1일
편집: James Tursa 2017년 10월 6일
No, you have to kill the Matlab process.

추가 답변(2개)

Peter Lawrence
Peter Lawrence 2017년 10월 6일
편집: Walter Roberson 2017년 10월 6일
Yes, it's part of the "undocumented" matlab stuff, but at least it works, and works well.
  댓글 수: 1
Mark Stone
Mark Stone 2017년 10월 6일
Nice. This addresses coding of a mex file so that it can be interrupted. However, it does not address the interruptibility of a mex file provided without source code. So if I understand correctly, I would still be out of luck if trying to run a mex file which was not designed to be interrupted and for which I don't have access to source code.

댓글을 달려면 로그인하십시오.

Victor 2016년 6월 16일

Who accepted that unacceptable answer!?

No but seriously this is sooooooooooooooooooooooooooooooooooooooooo annoying!

  댓글 수: 4
Pavel Holoborodko
Pavel Holoborodko 2020년 1월 23일
@"Plus, it is not clear to me what would happen in that 2nd link if the MATLAB Memory Manager was interrupted in the middle of something when its Worker Thread got terminated."
Suggestions to the situation are provided in the post. In short, WorkerThread must be used for computations, not for memory allocations (especially not by MATLAB Memory Manager functions). It is really bad idea to mix allocations & computations in (any) numerical code anyway.

댓글을 달려면 로그인하십시오.

Community Treasure Hunt

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

Start Hunting!

Translated by