Hello. Im still working on how to trace eval execution, but since is not posible using JSD I'm still looking for a mechanism that allow me instrument the code. I have been reading this material http://www.almaden.ibm.com/u/bartonjj/fireclipse/test/DynLoadTest/WebContent/DynamicJavascriptErrors.htm But does somebody has already passed trough this or might know where I should read (Documentation, API, etc). Thanks. Lautaro
On 26 juil, 18:48, John J Barton <[email protected]> wrote: > On Jul 26, 9:20 am, Lautaro Dolberg <[email protected]> wrote: > > > Hello, I'm working with the jsd services for trapping javascript > > execution but I noticed that the jsd.functionHook {onCall:} does not > > trap the eval() code. > > Is there any hook on the service for traping code executed via eval()? > > Thanks in advance. Lautaro Dolberg > > I don't understand your question. jsd.functionHook is called for JS > function call and return. eval() looks like a function but it is a > platform call and they don't show up in jsd.functionHook. > > Code executed via eval() is almost exactly like code executed by > <script> tag: > 1) Current flow is interrupted (page parsing for script tag, JS > function for eval). > 2) text is compiled, > 3) outer (aka top-level aka file-scope) function runs, > 4) Current flow continues. > (This similarity makes all the comments about eval being somehow evil > or special puzzling to me). > The funky thing about eval() in Mozilla's implementation is that the > file name is the outer file name and the line numbers make the > functions appear to overlay the outer source. That makes debugging > eval() impossible with jsd, > > jjb -- 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.
