I am receiving an error addressing tables in debug mode

This may be an error in the MATLAB source code, but I'm having issues with addressing tables when debugging code. This is happening consistently.

For example, tables receive an error: "Index exceeds matrix dimensions." whenever I try to access data using: indices, column names as string, or anything. It will work sometimes after I quit the debugging and re-run the code.

What's going on? Why am I having such an issue addressing tables? Is this a software bug

Here's an example of what causes a problem:

% Generic Code: Make a table
X = table((1:26)', cellstr(char(65:65+25)'),'VariableNames', {'Numbers', 'Letters'});
row1col2 = X(1,2); %addressing the first row, second column creates an error: Index exceeds matrix dimensions

Answer 1

[Peter Perkins]

In the debugger, when stopped in a method of a class, you are in effect "inside" the table, and none of the overloaded subscripting is called. table has overloaded subscripting, which is why you're seeing this, but the general idea is not specific to table. It's how the debugger interacts with the object system, and is what's needed to be able to debug a class's protected/private code.

You can call subsref directly, though.

Answer 2

[Shio Williams]

Hi Peter,

Thank you for the reply. I am not debugging from within the subsref function. I am debugging from within the code of a GUI, so technically my workspace should be similar to that of the Base with a few exceptions. Does that answer still apply?

[Peter Perkins]

It seems like you might have an unusual situation that is best handled by contacting MathWorks support directly.