R2022a problem: Line number missing in error message sent to Command Window.
54 views (last 30 days)
Show older comments
Scott MacKenzie on 19 Apr 2022
Commented: Sergio Roche on 29 Sep 2022
With R2022a, line numbers are sometimes omitted in error messages. Here's an example using a trivial script:
If I run the same script in R2021b, here's the result:
Weird. What's going on?
Is there a way to fix this in R2022a?
David Szwer on 17 May 2022
I get this problem too; also regarding tables, but a different error.
Error using ProcessMovement
All tables being vertically concatenated must have the same number of variables.
Error in ProcessAll (line 10)
[moving, moveN] = ProcessMovement(filedir, 0);
Note that ProcessAll and ProcessMovement are both functions. Back in the day, Matlab wouldn't show line numbers at all if the error was in a script; this isn't a reversion to that behaviour, it is something different.
Siddharth Bhutiya on 18 May 2022
This is a bug, thank you for reporting it! I have passed it along and it will be fixed in a future release.
Here is the bug report for this: https://www.mathworks.com/support/bugreports/2608278
As mentioned in the bug report, while this is being fixed, you could use MException.last.stack(1) to see the line number.
Sergio Roche on 29 Sep 2022
The new question for reference: https://www.mathworks.com/matlabcentral/answers/1814220-calling-the-error-function-does-not-print-the-line-number-in-r2022b
More Answers (0)
Find more on Debugging and Analysis in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!Start Hunting!