Bug #75096 Unable to debug a store procedure with mysql for visualstudio
Submitted: 3 Dec 2014 15:59 Modified: 17 Jan 2015 8:05
Reporter: Yves SCOTTO Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Visual Studio Integration Severity:S2 (Serious)
Version:1.2.3 OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[3 Dec 2014 15:59] Yves SCOTTO
I try to debug a store procedure with MySQL for Visual Studio 1.2.3
I have a Visual Studio version 8 and a mysql connector 6.8.4
When I try to debug a store procedure a always have "Error while debugging: PROCEDURE .serversidedebugger.Push does not exist.

I don't understand why because when I check the MySQL server, the .serversidedebugger database exists and the Push store procedure also

CREATE DEFINER=`root`@`localhost` PROCEDURE `Push`( pDebugSessionId int, pRoutineName varchar( 64 ) )

    insert into `.serversidedebugger`.`debugcallstack`( DebugSessionId, RoutineName ) values ( pDebugSessionId, pRoutineName );


I try to debug first on a remote MySQL server then on a local MySQL server and it is always the same error

I use the mysql root account the connect so I don't think that it's a privilege issue !

Any idea about this error 
Thank you

How to repeat:
Clic on "Debug MySQL routine"
[17 Dec 2014 8:05] Chiranjeevi Battula
Hello Yves SCOTTO,

Thank you for the bug report.
I tried to reproduce the issue at my end using Visual Studio 2013 (VB.Net), MySQL Connector/Net 6.9.5 but Couldn't trace out any issue in debug a store procedure and please find out screenshots.

Could you please list out the steps you tried out at your end? Please provide repeatable test case in order for us to confirm this issue at our end.

[17 Dec 2014 8:06] Chiranjeevi Battula
Store Procedure debug screenshots

Attachment: screenshots.zip (application/x-zip-compressed, text), 182.54 KiB.

[17 Dec 2014 8:07] Chiranjeevi Battula
please refer the link

[18 Jan 2015 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".