The Sad State of Debug Performance in C++

Re:The Sad State of Debug Performance in C++ by adrian_b on Monday September 26, 2022 @09:50AM (#32983099)

While I agree with you and with the OP and I have also been sometimes annoyed by this kind of debugger messages, the more universal solution than wanting an improved debugger is to rely for debugging on some form of progress and error logging in your program, which will work at any optimization level.

Adding such debugging aids in your program may need some extra work, but it also functions in all cases when using the debugger is hopeless, e.g. for concurrent programs or other programs that depend on real-time interactions which prevent the use of breakpoints.

[ Parent | on HN ]

Re:The Sad State of Debug Performance in C++ by usefulcat on Monday September 26, 2022 @02:46PM (#32986710)

Yes and no. I use logging too, but that's only useful when I know (or can guess) ahead of time what locations and what things at each location I'll need to know in order to diagnose the problem.

Of course I can always go back and add some logging, but it's not a given that I'll want to keep it around after the problem is fixed. For example if it's in a performance-critical section of code, even the cost of checking to see whether logging is enabled may be too great. And in any case every log statement does add visual noise to the code.

[ Parent | on HN ]