Getting variables in function workspace during debugging

7 次查看(过去 30 天)
I'm creating a mlapp data visualization tool and need to grab all variables in the current function workspace when debugging.
When running the app, while debugging a program, the user should be able to press a button when a breakpoint is reached to pull in all variables in the current function workspace to interact with the var data in the app. One main challenge is when this button is pressed, it goes into a callback function, which has its own function workspace within the app. I am using the below code to get each variable and do what I need to do with it:
variables = evalin('base', 'whos')
for ii = 1:numel(variables)
data = evalin('base', variables(ii).name);
% ....
% do something with data
% ....
end
I understand that 'base' is not what we want here. However, evalin only accepts 'base' and 'caller' and 'caller' is not correct either since it's a function of the app. So this is unable to grab the variables within the current function workspace when debugging, only the base workspace. Do you have any idea how to grab the variables for the current function you are in programmatically, while debugging?
  7 个评论
Matt F
Matt F 2022-3-22
@Michael Van de Graaff No I have not. My current solution is to call a function using a "favorite command" to update the variables since that will always run in the current workspace even when debugging.

请先登录,再进行评论。

回答(1 个)

Steven Lord
Steven Lord 2022-3-7
I'm creating a mlapp data visualization tool and need to grab all variables in the current function workspace when debugging.
When you enter debug mode you can switch between function workspaces via icons in the Editor or via the dbup and dbdown functions.
When running the app, while debugging a program, the user should be able to press a button when a breakpoint is reached to pull in all variables in the current function workspace to interact with the var data in the app.
Suppose that the variables in the "current function workspace" have the same name as "data in the app". Are you okay with the "data in the app" being overwritten by some other data (which may or may not be the same size or type or have the same meaning) that happens to have the same name?
Do you have any idea how to grab the variables for the current function you are in programmatically, while debugging?
IMO the answer is "You shouldn't." If you need to check something in the caller's workspace (to check that what your function received is what you expected it to receive) switch workspaces and check the value in situ then switch workspaces back to the workspace where you entered debug mode.
  1 个评论
Matt F
Matt F 2022-3-7
编辑:Matt F 2022-3-7
When you enter debug mode you can switch between function workspaces via icons in the Editor or via the dbup and dbdown functions.
This is true but unfortunately will not work in my case. Once you press the button in the app, dbup and dbdown no longer work since you enter the button callback and are no longer in debug mode.
Suppose that the variables in the "current function workspace" have the same name as "data in the app". Are you okay with the "data in the app" being overwritten by some other data (which may or may not be the same size or type or have the same meaning) that happens to have the same name?
This will never happen because all I am doing is taking the data from the variables in the function workspace and putting it into a WorkspaceTree for the user to view.
IMO the answer is "You shouldn't." If you need to check something in the caller's workspace (to check that what your function received is what you expected it to receive) switch workspaces and check the value in situ then switch workspaces back to the workspace where you entered debug mode.
This is the whole point of the app though. To be able to run the app, while debugging or just generally working in matlab, and inspect your variables and do data analysis on them.

请先登录,再进行评论。

类别

Help CenterFile Exchange 中查找有关 Debugging and Analysis 的更多信息

Community Treasure Hunt

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

Start Hunting!

Translated by