As far as I know, the source code is the only documentation for jsd.
You can try asking Mozilla, it's their code.  I gave up on that
approach long ago, since I was not able to get any information.

Alternatively you can ask here and I'll tell you what I've learned by
trial and error. By calling the functions, examining the returned
values, and reading their source we can piece together what the code
does.

A good starting point is the interface definition file:

http://mxr.mozilla.org/mozilla1.9.2/source/js/jsd/idl/jsdIDebuggerService.idl

frame is a jsdIStackFrame, type is an integer that is not very useful
except for debugging, and rv is the return value, generally not used.
Most of the calls backs must return one of the integers defined in the
interface as RETURN_*.

The parameters are available as shown in Firebug's lib.js function
getArgumentsFromObjectScope.

You might be interested in our work plan for Firebug 1.7, which
involves re-writing all of our code for js debug to support remote JS
debug. We will introduce a new API between debugger.js (script panel)
and jsdIDebuggerService (firebug-service) that will allow Crossfire to
sit in between.

jjb

On Jul 27, 1:58 am, Lautaro Dolberg <[email protected]> wrote:
> Hello
> I'm kind of lost in JSD documentation. I mean when I'm inside
> jsd.functionHook, or jsd.debugHook, there are functions:  onCall:
> function(frame, type, rv)  and onExecute: function(frame, type, rv)
> I would like to know where I can find the documentation of what
> methods or observer do the frame, type and rv parameters have.
> I'm looking for tracing information about the parameters of an
> executed function that has been trapped by any of 2 hooks.
> Thanks in advance. Lautaro

-- 
You received this message because you are subscribed to the Google Groups 
"Firebug" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/firebug?hl=en.

Reply via email to