How do I get rid of the K>> prompt?

Question

Stacey 2016-5-10

1
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/283542-how-do-i-get-rid-of-the-k-prompt

回答： ABDULMAJEED ALYAZIDI 2023-2-28

I keep getting stuck in K>> mode. I've tried hitting return several times, typing dbquit, home, and clc. None of these work. I'm using version R2015b. Thanks in advance for your help.

1 个评论
显示 -1更早的评论隐藏 -1更早的评论

Stephen23 2016-5-10

在 MATLAB Online 中打开

To quit the debugger:

press Shift + f5

or call

dbquit

To continue running the code:

press f5

http://www.mathworks.com/help/matlab/ref/dbquit.html

IMPORTANT: calling dbquit or shift+f5 does not clear the breakpoints from your files: as the documentation clearly states "All breakpoints remain in effect". So the next time the function runs (either by calling it or within a loop or callback) then MATLAB will enter debug mode again.

If the code is looping then you can use conditional breakpoints to avoid this.

Also if you have nested debugs then this only escapes the highest level debug mode...

http://www.mathworks.com/help/matlab/debugging-code.html

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Guillaume 2016-5-10

4
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/283542-how-do-i-get-rid-of-the-k-prompt#answer_221609

在 MATLAB Online 中打开

You've got a K>> prompt because you've entered debug mode within a function, either because you put a breakpoint there yourself, or because you've issued a dbstop if error and an error occurred in the function.

home and clc will have no effect on that, but despite what you say dbquit will leave debug mode. If you still have a K>> prompt after dbquit is because you've reentered debug mode while already in a debug session. If you issue enough dbquit you will eventually leave debug mode.

Most likely, you're in this situation because you've issued dbstop if error, hit an error and thus entered debug mode, try to run the function that produced the error without leaving debug mode, meaning that you've entered a new debug mode again, and done that a few more times. So you're in a K>> prompt within a K>> prompt within a K>> prompt, ...

To escape from all these recursive debug sessions:

dbquit all

To stop entering debug mode on error:

dbclear if error