splitapply does not retain ME stack

2026 1 15
2 个回答
回答已采纳
更新时间：2026 1 28
11 次查看（30 天）

1 个投票

When the function that splitapply throws an error, this line number of this error is not include in the output (matlab2024b)
Example:
T=table([1:3]');
G=findgroups(T);
splitapply(@fun, T, G);
function out = fun(varargin)
ERROR
end
This returns:
Error using splitapply>localsplitandapply (line 196)
Unable to apply the function 'fun' to the 1st group of data.
Error in splitapply (line 135)
varargout = localsplitandapply(fun,dataVars,gdiffed,sgnums,gdim,nargout);
Error in templateLoopOverAll (line 231)
splitapply(@fun, T, G);
Caused by:
Unrecognized function or variable 'ERROR'.
I was expeting that the line number that actually caused that error would be included:
Error in testfile>fun (line 5)
ERROR
Error in testfile (line 3)
fun()
Missing this information makes the debugging of fun very challenging.
How to retrieve this line number?

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

 采纳的回答

Vasco
Vasco 2026-1-28

0 个投票

The solution is to alter in splitapply.m line 242 from:
throwAsCaller(addCause(MException(m.Identifier,getString(m)),ME));
to:
rethrow(addCause(ME, MException(m.Identifier,getString(m))));

更多回答（1 个）

Matt J
Matt J 2026-1-15
编辑：Matt J 2026-1-15

0 个投票

Run with Pause on Errors.
Then the code will stop at the offending line:

6 个评论
显示 4更早的评论 隐藏 4更早的评论

Matt J
Matt J 2026-1-15
Youc an also invoke Pause on Errors from the command line with,
>> dbstop if error
Vasco
Vasco 2026-1-19
编辑：Vasco 2026-1-19
dbstop if caught error
That works!
From the menu it does not work:
  • This does not work on my installation, it stops at splitapply.m line 196
  • That seems not to work when I press: run this section (crtl-enter) -> it does not stop at al
Matt J
Matt J 2026-1-19
编辑：Matt J 2026-1-19
dbstop if error should be sufficient in R2024b when the script is run in full. My demo above used that.
The other observations are intended behavior.
Vasco
Vasco 2026-1-28
That indeed halts the debugger at this place, but it also halts the debugger in many other places (for example in some of the plotting functions). This makes it hardly usable.
Matt J
Matt J 2026-1-28
编辑：Matt J 2026-1-28
I use it all the time and have never had a problem with it stopping in plotting functions.
'dbstop if caught error' is usually more prone to stop in places you don't want, and will fail to stop at explicit errors that you do want to intercept.

请先登录，再进行评论。

类别

在 帮助中心 和 File Exchange 中查找有关 Debugging and Analysis 的更多信息

产品

版本

R2024b

标签

Community Treasure Hunt

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

Start Hunting!

Translated by