Breakpoint when Debugger Starts

I wonder if it is necessary really to have a quasi-breakpoint at the first line of the code every time the debugger starts.

Isn’t more practical (one keypress less) if the debugger stops at the first breakpoint which it sees after its starts?

Thank you.

Isn’t more practical (one keypress less) if the debugger stops at the first breakpoint which it sees after its starts?

When the debugger starts it does not execute any code until the user decide it.
The user might want to run 1 step, run to a breakpoint or do nothing by now.

Maybe the Editor should do nothing instead of going to the first line or go to the first line of executable code: address = 0.

arcachofo wrote:

Isn’t more practical (one keypress less) if the debugger stops at the first breakpoint which it sees after its starts?

When the debugger starts it does not execute any code until the user decide it.
The user might want to run 1 step, run to a breakpoint or do nothing by now.

Maybe the Editor should do nothing instead of going to the first line or go to the first line of executable code: address = 0.

Your two remarks are also valid. I personally prefer the latter one:
"... go to the first line of executable code: address = 0."