Comments on: Using ‘dbstop if error’ and conditional breakpoints to debug MATLAB https://blogs.mathworks.com/videos/2013/04/08/using-dbstop-if-error-and-conditional-breakpoints-to-debug-matlab/?s_tid=feedtopost Stuart uses video to share his experiences solving problems with MATLAB day-to-day, interesting new features, plus tips and tricks he has picked up along the way. Tue, 30 Apr 2013 22:28:41 +0000 hourly 1 https://wordpress.org/?v=6.2.2 By: Yair Altman https://blogs.mathworks.com/videos/2013/04/08/using-dbstop-if-error-and-conditional-breakpoints-to-debug-matlab/#comment-22512 Tue, 30 Apr 2013 22:28:41 +0000 https://blogs.mathworks.com/videos/?p=1077#comment-22512 I use dbstop if error all the time, for many years. In fact it’s even in my startup.m script. However, users should be aware that it has some drawbacks on the latest Matlab releases:

1. It clashes with GUIDE, making GUIDE unusable (verified bug reference 1-MH5KVI)
2. It apparently causes memory leaks in the new desktop Editor, causing increasingly large delays whenever a breakpoint is encountered and exited (unverified, but also reported by others in forums)

Hopefully these bugs will be solved soon, since this is such an important debugging mechanism.

]]>