See firebug/firebug.next#42

Florent

How does FBTrace render expandable objects across processes or does it?

There are many logs in the native tools and it would be great if those also appear in the tracing console.

Native tools use:

1. a pref to make those logs visible: "devtools.debugger.log"
2. and system dump() to display the result in the system console.

See e.g.
https://mxr.mozilla.org/mozilla-central/source/browser/devtools/debugger/debugger-controller.js#2296

Any tips how we could do this?

Honza

Does this extension still work in Firefox 49+? If not, is there an alternative console that allows for switching logging groups on and off?

Identify error message in logged object parse associated stack-frames and pretty print in the UI (PropertyTree).

Error message example:

"[JavaScript Error: "Error occurred while creating actor 'undefined: Error: Unable to load actor module 'resource://firebug-next-at-getfirebug-dot-com/data/logger-actor.js'.\nModule resource://firebug-next-at-getfirebug-dot-com/data/logger-actor.js is not found at resource://firebug-next-at-getfirebug-dot-com/data/logger-actor.js\nRegisteredActorFactory/this._getConstructor@resource://gre/modules/devtools/server/actors/common.js:42:15\nObservedActorFactory.prototype.createActor@resource://gre/modules/devtools/server/actors/common.js:108:11\nDebuggerServerConnection.prototype._getOrCreateActor@resource://gre/modules/devtools/server/main.js:1259:16\nDSC_onPacket@resource://gre/modules/devtools/server/main.js:1404:17\nLocalDebuggerTransport.prototype.send/<@resource://gre/modules/devtools/transport/transport.js:545:11\nmakeInfallible/<@resource://gre/modules/devtools/DevToolsUtils.js:83:14\nmakeInfallible/<@resource://gre/modules/devtools/DevToolsUtils.js:83:14\n\n\nStack: RegisteredActorFactory/this._getConstructor@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/common.js:44:15\nObservedActorFactory.prototype.createActor@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/common.js:108:11\nDebuggerServerConnection.prototype._getOrCreateActor@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/main.js:1259:16\nDSC_onPacket@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/main.js:1404:17\nLocalDebuggerTransport.prototype.send/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/transport/transport.js:545:11\nmakeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/DevToolsUtils.js:83:14\nmakeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/DevToolsUtils.js:83:14\nLine: 44, column: 14" {file: "resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/main.js" line: 1290}]"

STR:

1. Open Tracing console, check e.g. inspector/inspector-overlay option
2. Restart Firebug, open the toolbox select the Inspector panel
3. There should be logs in the tracing console, but nothing is there -> BUG

Honza

It's currently almost impossible to follow stack frame URLs for exception objects. See the stack field (and fileName) on the following screenshot.

The stack field contains individual frames separated by \n characters and every frame URL can be composed from several URLs separated by -> where the last URL is usually the important one.

I think that the last URL should be displayed by default. It should also be expandable to see the entire URL loader path (the other preceding parts).

STR:

1. Put the following code in main.js

try {
    asdfasd.asdfa = asdf;
}
catch (err) {
    TraceError.sysout("EXCEPTION " + err, err);
}

2. Check ERRORS option in the Tracing Console

3. Launch Firefox+Firebug and check out the console, there should be one exception. Open it and select the Object tab.

Stack frame URLs should be displayed as a list of links that open the Source View when clicked.

Honza

I guess the functionality existed but went away with the DOM panel refactoring in Firebug 2.0?