Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Lua Development Tools » Vendor specific debug protocol commands
Vendor specific debug protocol commands [message #1148919] Mon, 21 October 2013 20:46 Go to next message
Dan Jackson is currently offline Dan Jackson
Messages: 12
Registered: October 2013
Junior Member
I see that the DBGp protocol (xdebug.org/docs-dbgp.php#extended-commands) talks a little about how vendor specific commands are to be named. Is there any guidance on implementing those commands in your LDT client or server?

Specifically, how would you recommend the LDT plugins be changed to accomodate vendor specific commands? And is there a preferred integration point in debugger.lua for doing the same -- like calling out to a vendor-specific module or do we need to change our version of debugger.lua to handle these cases?

Thanks very much
Dan Jackson
Re: Vendor specific debug protocol commands [message #1151686 is a reply to message #1148919] Wed, 23 October 2013 14:27 Go to previous messageGo to next message
Simon Bernard is currently offline Simon Bernard
Messages: 286
Registered: July 2009
Senior Member
Hi Dan,
I'm not the main developer of debugger code and I'm not aware about a way to add a vendor specific command. Maybe you could have a look at :
- debugger.commands module at lua/client side.
- IDbgpSession, IDbgpCoreCommands,... and all interface in DLTK package org.eclipse.dltk.dbgp.commands for eclipse/server side. You could take a look at that too .

HTP

Simon
Re: Vendor specific debug protocol commands [message #1152022 is a reply to message #1151686] Wed, 23 October 2013 19:25 Go to previous messageGo to next message
Dan Jackson is currently offline Dan Jackson
Messages: 12
Registered: October 2013
Junior Member
Thanks for the pointers Simon, I'll take a look.
-Dan
Re: Vendor specific debug protocol commands [message #1152093 is a reply to message #1148919] Wed, 23 October 2013 20:24 Go to previous messageGo to next message
Julien Desgats is currently offline Julien Desgats
Messages: 6
Registered: August 2012
Junior Member
Hi Dan,

It depends of what you are trying to accomplish.

If you want to be able to inspect some custom userdata, a new feature called "inspectors" will be integrated soon in LDT. It will allow you to provide a custom introspection function which decode customs objects (read only for now). See the associated bug for details. Basically a quite simple Lua hook can decode any custom table or userdata.

But if you want to really add commands, like Simon said, you have to add support of it on both debugger and IDE sides. There is no strict policy about adding extra features to DBGp protocol, LDT does this for coroutine handling: a new command "coroutine_list" has been added, and some standards commands takes an extra "-o" parameter to operate on a paused coroutine.

Adding a command in debugger is not so complex, just an extra handle to add in "debugger.commands" (you can monkey patch it, modifying source is not needed).

On IDE side, it's a bit more cumbersome as most of DBGp support is provided by DLTK framework and extending it may be difficult (coroutine management required a ton of hacks IIRC).
Re: Vendor specific debug protocol commands [message #1153092 is a reply to message #1152093] Thu, 24 October 2013 11:25 Go to previous message
Dan Jackson is currently offline Dan Jackson
Messages: 12
Registered: October 2013
Junior Member
Thanks for the advice Julien. I will need to add new commands to provide non-Lua information that is unique to our execution environment back to the IDE. Looks like I've got some work cut out for me on the DLTK side.
Thanks again
Dan
Previous Topic:Koneki LDT stops after stepping twice
Next Topic:Spellcheck Support
Goto Forum:
  


Current Time: Wed Oct 01 14:27:56 GMT 2014

Powered by FUDForum. Page generated in 0.06591 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software