console.log already generates representation disconnected from the heap, it
abbreviates strings with a hard-coded threshold and goes 1 level deep (i.e.
does not dive into the composite objects).
We can dump scopes using it, but I wonder whether it generates too much
noise (scopes are chained and the dumps can get really large). So you also
might want to control the depth of enclosing scopes to dump.
Another concern is that we currently operate scopes in debugger only (i.e.
while stopped), so it is not that easy to implement - we would need to get
scope info at runtime. Depending of the complexity of these we might decide
to hold it off.
I wonder if special-casing console.log(arguments) to dump all its items
would cover a percentage of your needs. In either case, please file a bug
On Sep 18, 2012 1:31 AM, "John J Barton" <johnjbar...@johnjbarton.com>