Ah yeah, I have a patch pending for that which optionally includes the code in builds, but still gates the printing behind a flag. I'll upload it tomorrow.
On Mon, 15 May 2017, 21:51 Adam Klein, <[email protected]> wrote: > As I've been doing some work on Ignition, I've found tracing to be very > useful. However, the current setup seems a bit clumsy. Since we no longer > build the handler generation code into the binary, it seems we now have to > have tracing always-on or always-off for a build (controlled by the gn > option "v8_trace_ignition"). This spams the console with lots of output, > even during build (since mksnapshot runs with the argument as well). And > there's not even a way to turn it off at runtime (at least from what I can > tell). > > I'm happy for the binary size saving, but I wonder if, for development > purposes, there's some other middle ground that would allow us to keep > tracing as a runtime option in development builds. > > Thoughts? > > - Adam > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
