[Maria-discuss] Stored Procedure debugger from Peter Gulutzan and Trudy Pelzer
Hi, Peter Gulutzan and Trudy Pelzer announced their GUI debugger for stored procedures. Sources, binaries and a demo are available here: http://ocelot.ca/blog/blog/2015/03/02/the-ocelotgui-debugger/ This is a great news. Greetings.
I don't want to show critisism against projects like this - I hope that this is clear. There are many debuggers, and they are more than welcome. Even Oracle has a debugger, if you use Windows and Visual Studio (sigh). But I still think that MariaDB needs a native debug API, which fully supports checkpoints/flow control, context inspection and exposes the call stack. I doubt that an external debugger that transparently adds debug code could possibly replace it, especially if your business logic is complex. I've tried to write a debug library in SQL - the problems I've found make me seriously doubt on the possibility to follow this path. Regards Federico -------------------------------------------- Mar 10/3/15, Alexander Barkov <bar@mariadb.org> ha scritto: Oggetto: [Maria-discuss] Stored Procedure debugger from Peter Gulutzan and Trudy Pelzer A: "Maria Discuss" <maria-discuss@lists.launchpad.net> Data: Martedì 10 marzo 2015, 11:42 Hi, Peter Gulutzan and Trudy Pelzer announced their GUI debugger for stored procedures. Sources, binaries and a demo are available here: http://ocelot.ca/blog/blog/2015/03/02/the-ocelotgui-debugger/ This is a great news. Greetings. _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Hi Federico, On 03/10/2015 04:17 PM, Federico Razzoli wrote:
I don't want to show critisism against projects like this - I hope that this is clear. There are many debuggers, and they are more than welcome. Even Oracle has a debugger, if you use Windows and Visual Studio (sigh).
The debugger supports the things you mention. At least during my 10 minute trial I experimented with breakpoints and context inspection, everything worked like a charm. I don't know about inspecting the call stack, didn't try to. But it seems it does.
But I still think that MariaDB needs a native debug API, which fully supports checkpoints/flow control, context inspection and exposes the call stack. I doubt that an external debugger that transparently adds debug code could possibly replace it, especially if your business logic is complex. I've tried to write a debug library in SQL - the problems I've found make me seriously doubt on the possibility to follow this path.
Regards Federico
-------------------------------------------- Mar 10/3/15, Alexander Barkov <bar@mariadb.org> ha scritto:
Oggetto: [Maria-discuss] Stored Procedure debugger from Peter Gulutzan and Trudy Pelzer A: "Maria Discuss" <maria-discuss@lists.launchpad.net> Data: Martedì 10 marzo 2015, 11:42
Hi,
Peter Gulutzan and Trudy Pelzer announced their GUI debugger for stored procedures.
Sources, binaries and a demo are available here:
http://ocelot.ca/blog/blog/2015/03/02/the-ocelotgui-debugger/
This is a great news.
Greetings.
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
But it depends on functionalities available only in a Linux shell, I think, and is not cross-platform? Further I agree with Federico that it is a server-side *API* we need, so that functionalities are exposed to any client that wants to use it. -- Peter On Thu, Mar 12, 2015 at 7:48 AM, Alexander Barkov <bar@mariadb.org> wrote:
Hi Federico,
On 03/10/2015 04:17 PM, Federico Razzoli wrote:
I don't want to show critisism against projects like this - I hope that this is clear. There are many debuggers, and they are more than welcome. Even Oracle has a debugger, if you use Windows and Visual Studio (sigh).
The debugger supports the things you mention. At least during my 10 minute trial I experimented with breakpoints and context inspection, everything worked like a charm. I don't know about inspecting the call stack, didn't try to. But it seems it does.
But I still think that MariaDB needs a native debug API, which fully
supports checkpoints/flow control, context inspection and exposes the call stack. I doubt that an external debugger that transparently adds debug code could possibly replace it, especially if your business logic is complex. I've tried to write a debug library in SQL - the problems I've found make me seriously doubt on the possibility to follow this path.
Regards Federico
-------------------------------------------- Mar 10/3/15, Alexander Barkov <bar@mariadb.org> ha scritto:
Oggetto: [Maria-discuss] Stored Procedure debugger from Peter Gulutzan and Trudy Pelzer A: "Maria Discuss" <maria-discuss@lists.launchpad.net> Data: Martedì 10 marzo 2015, 11:42
Hi,
Peter Gulutzan and Trudy Pelzer announced their GUI debugger for stored procedures.
Sources, binaries and a demo are available here:
http://ocelot.ca/blog/blog/2015/03/02/the-ocelotgui-debugger/
This is a great news.
Greetings.
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Dear Alexander Barkov, Thanks for looking at the debugger feature of Ocelot's open-source GUI client. As you saw, ocelotgui supports breakpoints, flow control, and context inspection. Recently we added call-stack viewing and variable-changing, in the source downloads. The early-alpha release works on Linux. It does not require any Linux-only features, and the tools (C++ and Qt) are reputedly portable. Peter Gulutzan
license? On Thu, Mar 12, 2015 at 8:46 PM, Peter Gulutzan <pgulutzan@ocelot.ca> wrote:
Dear Alexander Barkov,
Thanks for looking at the debugger feature of Ocelot's open-source GUI client. As you saw, ocelotgui supports breakpoints, flow control, and context inspection. Recently we added call-stack viewing and variable-changing, in the source downloads.
The early-alpha release works on Linux. It does not require any Linux-only features, and the tools (C++ and Qt) are reputedly portable.
Peter Gulutzan
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Hi, So I can run a SELECT my_func(blah) from some_table; and a breakpoint will fire if my_func calls another function which calls another function and that function has a breakpoint ? I fail to see how that is possible, but if it is, please provide a technical description of how it works if it is. I really think a debugging API is needed for such functionality. --Justin On Thu, Mar 12, 2015 at 12:46 PM, Peter Gulutzan <pgulutzan@ocelot.ca> wrote:
Dear Alexander Barkov,
Thanks for looking at the debugger feature of Ocelot's open-source GUI client. As you saw, ocelotgui supports breakpoints, flow control, and context inspection. Recently we added call-stack viewing and variable-changing, in the source downloads.
The early-alpha release works on Linux. It does not require any Linux-only features, and the tools (C++ and Qt) are reputedly portable.
Peter Gulutzan
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Replying to Justin Swanhart: (Apologies if this doesn't appear at the right spot in the thread, I haven't figured this system out.) Yes, run SELECT my_func(blah) from some_table; and a breakpoint will be seen if my_func calls another function which calls another function and that function has a breakpoint. That's not much different from what's in the demo which is illustrated on ocelot.ca/blog. For this early alpha all we offer as an 'internals manual' is the code comments, but there are lots of them. Peter Gulutzan On 03/12/2015 06:00 PM, Justin Swanhart wrote:
Hi,
So I can run a SELECT my_func(blah) from some_table; and a breakpoint will fire if my_func calls another function which calls another function and that function has a breakpoint ? I fail to see how that is possible, but if it is, please provide a technical description of how it works if it is. I really think a debugging API is needed for such functionality.
--Justin
On Thu, Mar 12, 2015 at 12:46 PM, Peter Gulutzan <pgulutzan@ocelot.ca <mailto:pgulutzan@ocelot.ca>> wrote:
Dear Alexander Barkov,
Thanks for looking at the debugger feature of Ocelot's open-source GUI client. As you saw, ocelotgui supports breakpoints, flow control, and context inspection. Recently we added call-stack viewing and variable-changing, in the source downloads.
The early-alpha release works on Linux. It does not require any Linux-only features, and the tools (C++ and Qt) are reputedly portable.
Peter Gulutzan
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss <https://launchpad.net/%7Emaria-discuss> Post to : maria-discuss@lists.launchpad.net <mailto:maria-discuss@lists.launchpad.net> Unsubscribe : https://launchpad.net/~maria-discuss <https://launchpad.net/%7Emaria-discuss> More help : https://help.launchpad.net/ListHelp
Hi, Great, I'll check it out. It sounds like a very nice tool. Thanks for developing it. Sent from my iPhone
On Mar 13, 2015, at 8:12 AM, Peter Gulutzan <pgulutzan@ocelot.ca> wrote:
Replying to Justin Swanhart: (Apologies if this doesn't appear at the right spot in the thread, I haven't figured this system out.) Yes, run SELECT my_func(blah) from some_table; and a breakpoint will be seen if my_func calls another function which calls another function and that function has a breakpoint. That's not much different from what's in the demo which is illustrated on ocelot.ca/blog. For this early alpha all we offer as an 'internals manual' is the code comments, but there are lots of them.
Peter Gulutzan
On 03/12/2015 06:00 PM, Justin Swanhart wrote: Hi,
So I can run a SELECT my_func(blah) from some_table; and a breakpoint will fire if my_func calls another function which calls another function and that function has a breakpoint ? I fail to see how that is possible, but if it is, please provide a technical description of how it works if it is. I really think a debugging API is needed for such functionality.
--Justin
On Thu, Mar 12, 2015 at 12:46 PM, Peter Gulutzan <pgulutzan@ocelot.ca> wrote: Dear Alexander Barkov,
Thanks for looking at the debugger feature of Ocelot's open-source GUI client. As you saw, ocelotgui supports breakpoints, flow control, and context inspection. Recently we added call-stack viewing and variable-changing, in the source downloads.
The early-alpha release works on Linux. It does not require any Linux-only features, and the tools (C++ and Qt) are reputedly portable.
Peter Gulutzan
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
participants (5)
-
Alexander Barkov
-
Federico Razzoli
-
Justin Swanhart
-
Peter Gulutzan
-
Peter Laursen