Something in CMDebug Causing Execution to Break

[CityguyUSA]

I'm sitting waiting for a command to execute in CMDebug and it's often not a command that should consume lots's of time like a call or maybe a complex statement might. At some point I say something isn't right. I can see by the grayed out debugger commands that it's still active. Then it dawns on me to look at the console. This is what I find but I have no answer as to why. As soon as I key that N it takes off again. Not like I hit Ctrl-C or something to cause it.

 

[rconn]

Impossible to reproduce without more information; preferably a reproducible failcase.

Are you using CMD or TCC syntax? You'll get those errors with CMD syntax, since CMD doesn't have a BREAKPOINT command.

 

[CityguyUSA]

I guess If I knew what was causing it I would tell you. But since it's your software you should tell me.

 

[CityguyUSA]

Yep same statement

 

[rconn]

I can't debug a batch file from a screenshot. If you can provide me with a batch file(s) that can demonstrate the problem and that isn't tied to anything exclusive to your system I will try to reproduce the issue here.

You can get the "Cancel batch job" message if the parser detects a ^C or ^Break, or if you have a (some of the) "ON xxx" statement , or if an internal command or library routine or plugin or Windows API throws an unhandled exception. You can also get it with a stack overflow or out of memory error.

 

[CityguyUSA]

I can't debug a batch file from a screenshot. If you can provide me with a batch file(s) that can demonstrate the problem and that isn't tied to anything exclusive to your system I will try to reproduce the issue here.

You can get the "Cancel batch job" message if the parser detects a ^C or ^Break, or if you have a (some of the) "ON xxx" statement , or if an internal command or library routine or plugin or Windows API throws an unhandled exception. You can also get it with a stack overflow or out of memory error.

I'm not getting any of those errors. It's stopping on the call statement which most likely means it was the previous statement another "if" statement.

There are breakpoints that don't work on the first lines of if's and the random statement transfer from what seems to be if statements. The variable value display issue on the if statements. I don't have any "on xxx" statements. If I were a betting man, and I'm not, I'd say maybe if the "if" problem is resolved this may resolve? Let's leave this till maybe there's some resolution of the if's and see if it corrects?