Remember that debugging is a process going backward. You have the end result - a bug - and find the cause, which preceded it. It's about working your way backward and, unfortunately, debuggers only step forwards. This is where good logging and postmortem analysis can give you much better results.
I keep wondering how does a debugger work? Particulary the one that can be 'attached' to already running executable. I understand that compiler translates code to machine language, but then how does
Vibe Coding is a fresh take in coding where users express their intention using plain speech, and the AI transforms that thinking into executable code. The goal of Vibe Coding is to create an AI powered development environment where AI agents serve as coding assistants making suggestions in real time, automating tedious processes, and even producing standard codebase structures.
Prepare your ILE program for debugging Start a debug session Add and remove programs from a debug session View the program source from a debug session Set and remove conditional and unconditional breakpoints Step through a program Display the value of variables Change the value of variables Display the attributes of variables Equate a shorthand name to a variable, expression, or debug command.
In Java/C# you can easily step through code to trace what might be going wrong, and IDE's make this process very user friendly. Can you trace through python code in a similar fashion?
Restarting Visual Studio seemed to fix it temporarily. Clicking the "X" button to close Visual Studio while debugging causes the "Do you want to stop debugging?" message box to pop up; while this message box is up, the symbols load at ordinary speeds. Once all the symbols are loaded, you can click "No" to cancel the close.
I want to debug the whole flow of a (Java) program. I see there are several options for stepping through my program. What is the difference between step into and step over?
The "Data Breakpoint" option under "Debug -> New Breakpoint" is disabled.. any idea why? It stays disabled wether or not I'm actually debugging or not. I'm using Visual Studio 2015.
Compiler does not need to "modify" the binary in any way to support the breakpoints. However it is important, that: Compiler includes enough information in the executable (that is not in the code itself but in special sections in same file), so that debugger can relate source that user wants to debug with machine code. One typical thing debugger needs to know to be able to set breakpoints ...
