How to make assert() debug break?

4 views (last 30 days)
Zohar on 5 Jul 2022
Commented: Zohar on 5 Jul 2022
I attached my solution. Not sure why it's not the default behavior.
function assert1( b )
if nargin < 1
b = 0;
if ~b
disp( 'Assertion failed.' );
if 0
dbstop in assert.m at 11;
dbclear in assert.m at 11;
ST = dbstack;
if length( ST ) > 1
ST = ST(2);
fl = ST.file;
ln = ST.line + 1;
cmd = [ 'dbstop in ' fl ' at ' int2str(ln) ];
eval( cmd )
  1 Comment
Jan on 5 Jul 2022
What is the behavior of your code? It creates a breakpoint in the next line and Matlab will stop there.
What happens in nested functions, functions attached to a script and in anonymous functions?

Sign in to comment.

Accepted Answer

Steven Lord
Steven Lord on 5 Jul 2022
Based on Jan's description (I have not read the code) you'd also want to think about what this does if you call assert1 at the MATLAB prompt, on the last line of a file, on the last line of a function, inside an eval call, in a P-coded file (I think this one might work), via mexCallMATLAB in a MEX-file, in a deployed application, ...
IMO there are certain functions that inherently require interactivity and so users won't be surprised if those functions behave interactively. input, uigetfile, and keyboard are examples of these. But if you call a function that requires interactivity in a function that doesn't, or if you make a function require interactivity that users' mental model says shouldn't require interactivity, that can be annoying to the point of unusability.
Imagine if (for example) the plot function prompted users for the X and Y data every time it was called. You couldn't use it in a program you intended to run unattended. Is users' mental model for assert more like input (where you expect it to require interactivity) or more like plot (start it running and let it do its thing)? To me having assert drop into debug mode would be quite annoying.
Besides, there is a way to get assert to stop and drop you into debug mode without requiring any changes to the functionality of assert or changes to code that calls assert. Set an error breakpoint. If the assert triggers it will cause an error which will be caught by the error breakpoint.
Zohar on 5 Jul 2022
Much better, I'm happy with that.
Up until now, everytime something asserted, I needed to relace "assert(b)" with "if b, assert".
I was looking for a behavior like in c++: in debug mode, assert breaks, in release it's skipped. These options let me attune matlab in the same spirit.

Sign in to comment.

More Answers (0)





Community Treasure Hunt

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

Start Hunting!