487548 - Need finer control over verbose mode

Status: RESOLVED FIXED

(Tamarin Graveyard :: Virtual Machine, defect)

Description

[Rick Reitmaier]

Currently verbose mode is an on/off proposition, based on the value in config at startup.

When debugging a large amount of AS code, this is quite troublesome in that megabytes of output can be easily produced.

One idea to limit the size of this output, would be to the build the verbose system around the concept of on/off trigger points.  Wherein the VM is always ready to produce output but only does so, when a given condition occurs.  Additionally it could cease output on a different or similar trigger.

As a first suggestion some useful trigger points might be method execution count, jit'd method count (ala jitmax) or PoolObject count.

Looking for more opinions...

Comment 1

[Lars T Hansen]

I agree this would be useful.

Class and method name / function name?

-Doz method=runTest
-Doz 'class=Button,method=.*handler'

Functions that contain certain ABC instructions?

(ObSilly, -Doz seems like an appropriate switch as Oz was a verbose wizard.)

Comment 2

[Steven Johnson]

(In reply to comment #1)

> (ObSilly, -Doz seems like an appropriate switch as Oz was a verbose wizard.)

yes, but he also insisted people shouldn't look behind the curtain, which is the point of this switch...

Comment 3

[Edwin Smith]

either this is done or the bug should be converted to a tracker for remaining work in other bugs.

Comment 4

[Rick Reitmaier]

I don't believe its done.   We have no patches for it and I'm not sure that it is a dup of any other bug.