Been there, done that just two months ago (it's a remote debugger with
a command-line interface). It's moderately involved... I did it as a
day job project at my company, so can't provide source code (and it
has some proprietary parts anyway, particularly the definition of a
script execution instance, as well as support for debugging across
continuation restarts). For what's it worth, the solution I created
has a separate server side and client side, and I created a simple
network protocol where the parties pass JSON messages through a TCP
connection, so it would be possible to use the protocol and fit a GUI
at the other end instead of the CLI.
If there's enough interest, I might try to strip out the proprietary
stuff and obtain permission to release it as open source (the company
is fortunately fairly friendly to open source).
Attila.
On 2009.05.01., at 23:15, SCWells72 wrote:
We're embedding Rhino in our system as an extensibility tool and
that's going very well. I imagine it would be very useful for
extenders of our system to be able to debug their scripts in a high-
level symbolic debugger. I found the Rhino debugger here:
http://www.mozilla.org/rhino/debugger.html
but it looks like that's intended to be used against a script file or
some other direct input.
I was wondering if anyone had any experience with using this debugger
against an embedded Rhino engine successfully. I imagine it's too
much to ask for remote debugging, but minimally if I could tell the
app to bring up the debugger window when (certain) scripts are
executing and allow me to set breakpoints, step through execution,
etc.
I searched the Rhino pages, this forum, and Google in general and
didn't find a clear answer. I apologize if this has been asked/
answered before.
Thanks!
Scott
_______________________________________________
dev-tech-js-engine-rhino mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
