dbForge MySQL 2020 Bug - Serious Debugging Issues

[Requnix]

This is a hard one to provide information for because I'm not sure how to reproduce it; the best I can do right now is encapsulate the debugging issues as best as possible - for clarity, the dbForge Studio 2020 Enterprise BETA has a crazy amount of debugging issues:

• I've received numerous "bogus" errors from the IDE when trying to initiate debugging stating a stored procedure parameter is not defined; when it clearly is -- and it executes fine without issue. It also often highlights red a blank/empty area when giving this error.
• I've had the debugger visual line representation go crazy; it will highlight lines of code in the IDE that are NOT the lines being executed.
• The debugger will get "lost" when diving into call after call after call; often resulting in no cursor location, and pressing F11 just causes the IDE to flicker.
• When trying to debug, I'll get the prompt to compile, followed by "A connection error has occurred. Try again later." Sometimes running the STEP INTO (F11) option resolves it; sometimes, I have to close out the tab for the stored procedure and re-open it.

I'll update this thread as I come across more. Sadly, I can't seem to reproduce these issues with efficiency; they are random and sporadic.

The debugger is nowhere near ready for release. I recommend focusing on debugger-related issues with top priority.

[alexa]

We will investigate this issue and will answer you as soon as possible.

[Requnix]

Thanks! Please contact me directly if you need any additional information. IMO these are red-flag issues that would prevent the release of 2020. Anything I can do to help.

BTW can we expect an updated BETA version in the next week or two for testing?

[Requnix]

I just created a SWF video showing the issues mentioned above. You can download it here: https://1drv.ms/u/s!Au1rXgEghmrshXZp9B1 ... z?e=o8RfwW

[alexa]

Could you please provide us the server's version?

You could try removing the cr_debug database. When starting the debug again, it will be created automatically.

[alexa]

The debugger will get "lost" when diving into call after call after call; often resulting in no cursor location, and pressing F11 just causes the IDE to flicker.

Could you please provide us the CREATE definition of the procedure causing the issue along with the CREATE definition of referenced procedure?

You can reply to our support desk at supportATdevartDOTcom.

[Requnix]

Server Version 8.0.18.

This issue happens with all stored procedures that are nested. I'll try deleting the debug system.