I am trying to make progress in testing code, but I encounter an error. No problem, just enable dbstop on error and run again. The error occurs about three layers down in the "ismissing" function. Boom, boom, boom! Three functions open up, and I am down in the "bowels of the machine." I don't understand that code, I can't touch that code, and it does me little good being down at that level of code. Why am I here? I have asked the function to operate on a cell array in a way that it cannot understand. I know that from the error statement. I don't need to be down in the middle of a private function. Even worse, now I am several workspaces below where I am actually working. So, I have to close all the functions, and the dbup several times back up the chain to where I am working, and where I want to remain.
Does anyone know of a way to restrict the debugger to remain in the current workspace, and not descend into Matlab's "private" function calls?