62
edits
User:GijsKruitbosch/JS Debugging: Difference between revisions
→__toplevel__ and disappearing scripts
mNo edit summary |
|||
| Line 51: | Line 51: | ||
== __toplevel__ and disappearing scripts == | == __toplevel__ and disappearing scripts == | ||
[this is only how I, Silver/James Ross, understand things] | |||
SpiderMonkey (and Mozilla's use of it) wont keep scripts around forever, of course, but some script objects die very quickly. One of these is refered to in Venkman as __toplevel__, and is the script object for the global scope in a webpage (for example). | |||
AIUI, it gets created first, when the <script> is seen/handled, and SpiderMonkey runs through it running the code and defining the functions. Once that's completed, it tends to go away. I don't know any details, this is just based on something someone (possibly Robert Ginda) said, or a comment in Venkman's code. | |||
The issue is that once the SpiderMonkey script object has evaporated, you can't get any information from it (duh), which means you can't calculate what lines you could set breakpoints on (they'd have to be future breakpoints). | |||