If I don't include cv::Mat test;
then the debugger works fine. The inclusion of that 1 line, for some reason, kills the Qt debugger.
Symptoms:
I'm not doing anything fancy (to my knowledge), so the settings should be the defaults on installation.
Version info:
I can't work with this anymore! Its slowed the debugging process down to a crawl just finding where the bugs are. The problem seems to be new, having only just started a few days ago. What's going on? How can I bring the debugger back to life without reinstalling Qt? Thanks in advance!
It's not OpenCV only. I have the same problem on Windows. the Windows Debugger (WinDbg) is horribly bad. Many times it freezes like you're describing and takes forever with that irritating waiting spinner. It's not even possible to view the value of a boost::filesystem::path
. Some times it doesn't even show variables that are there (like this
sometimes), and when I expand it in Qt Creator, they appear empty.
Therefore, I decided not to do hardcore debugging on Windows anymore. What I do, is do very shallow debugging on Windows, and hardcore debugging I do on Linux, with gcc and gdb. I have a virtual machine (VM Ware) that I use for this.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.