Firebug 1.7: Mozilla Backend

From FirebugWiki

Mozilla back-end represents an adapter between V8 like protocol and Mozilla JSD. This adapter lives in Firebug and implements BTI interface. This adapter should replace firebug-service in Firebug 1.7.

Contents 1 Resources 2 Implementation Details 3 Test Cases 3.1 Connect 3.2 Get Contexts 3.3 Compilation Unit 3.4 Get Source 3.5 Set Breakpoint 3.6 Get Stack Trace 3.7 Debugger Step 3.8 Disconnect

Resources

• V8 Debugger Protocol
• Crossfire
• Architecture Refactoring

Implementation Details

Corresponding BTI objects:

• BTI.Browser → Firebug firebug.js
• BTI.CompilationUnit → Firebug.SourceFile sourceFile.js
• BTI.StackFrame → FBL.StackFrame lib.js
• BTI.Breakpoint → Firebug.Breakpoint breakpoint.js
• BTI.BrowserContext → Firebug.TabContext tabContext.js
• BTI.JavaScriptContext → ?

What is the JavaScriptContext in the context of Firebug architecture? Can you describe relations among BTI objects?

Test Cases

Exploration of some real world scenarios that happens when debugging a web application. These scenarios describe in-process usage of the firebug-service through a BTI adapter. The basic concept is as follows:

Firebug UI (Script Panel) → BTI → FBS → JSD

Where is Firebug.Debugger in this concept?

Connect

Connect to the browser.

Get Contexts

Get list of all available contexts in the connected browser.

Compilation Unit

Get list of all compilation units for given context.

Get Source

Get source code (range) for given compilation unit.

Set Breakpoint

Set a breakpoint in given compilation unit.

Where the list of compilation units is stored?

What is the event/callback that allows to collect all compilation units?

Get Stack Trace

Get stack trace (aka backtrace) when a breakpoint hits.

Debugger Step

Perform a debugger step (step over, step into, continue)

Disconnect

Disconnect from the debugger