dbForge MySQL 2020 Bug - Start Debugging executes... doesn't debug

[Requnix]

If you select "start debugging" (Ctrl-F5) the system EXECUTES the code instead of starting the walk at the first line. You must select "step into" in order to truly start debugging.

[alexa]

We will fix this issue in the release of the new version 9.0 that should be available within a month's time.

[alexa]

Sorry for the confusion.

The Ctrl-F5 command is supposed to halt only on breakpoints.

The 'Step Into' needs to be used to halt on each line https://docs.devart.com/studio-for-mysql/debugging-stored-routine/execution-control.html

This is by design.

[Requnix]

Understood; but in 2019 when you'd hit F5 it would stop on the first line to let you know the debugging process has begun, allowing you to F5 continue or F11 step. IMO the issue is hitting F5 from the IDE should put you on the first line of code that's being debugged so you know what's going on rather than running it like an Execute. The behavior from 2019 IMO was proper. I think developers will expect the 2020 version to behave the same way. I sure did.

Note Visual Studio does this (the way 2019 does it). It's what developers expect.

Just a recommendation.