Debuggers actually set breakpoints after the function prologue, but reliably identifying the prologue across compilers and optimisation levels is hard!
miniblog.
Related Posts
Smalltalk is the only language I know of where you can have multiple debuggers, with different stacks, in the same instance.It's liberating.
Although 'time travelling debuggers' sound cool, I would find them easier to explain if we simply called them 'debuggers with undo'.
I'd previously thought time-travelling debuggers were impractical due to the CPU and memory overheads. Opt-in tools sidestep this. 2/2