3 ms·
Maybe I am biased because I work in embedded :) Before that I also encountered similar issues at the other end of the performance spectrum: When working with p
by Linux-Fan 3y ago
Maybe I am biased because I work in embedded :)
Before that I also encountered similar issues at the other end of the performance spectrum: When working with parallelized C++ code that required more than 64 GiB of RAM the overhead of a debugger can make the difference between being able to run the program or not.
I still believe that in almost all cases it is possible to use a debugger even there, but it is always a significant setup required.
And in the modern languages like Java and Python there are stack traces which already greatly help with the “debugging” such that even there I rarely missed the option to step through a program. I never worked with any really complicated Java or Python codebases, though.