TraceView Plus Support

If you need assistance with TraceView Plus, please contact us.

TraceView Plus FAQ

Expand All / Collapse All

  • When I am logging a trace to an .etl file, the file size grows quickly over time even if no trace messages are sent.

    Generally speaking, an .etl file is optimized for speed, not for size. If you are worried about size, compress the file. That said, if you flush the ETW buffers, a lot of zeros will be written to the .etl file. This may happen, for instance, if you make the flush timer (Session Properties) smaller than 1000ms.

  • When I view traces, the function and line number information are sometimes incorrect.

    When you enable compiler optimizations, especially with whole program optimization, the compiler enables automatic function inlining. When a function is inlined, the mapping between program code and debugger information is sometimes incorrect. This is similar to the effect when you step through optimized code. As a result, the function and line number information extracted from the PDB may be incorrect. You can compensate this effect by defining the macro WPP_EMIT_FUNC_NAME, however, the Jump To Source feature will not work correctly.