Would it be feasible to include code-coverage data within tracegl?

[vivin]

First of all, thank you for creating such a fantastic tool! It has cut down my debugging time significantly!

I was wondering if you would be able to add code-coverage information in tracegl? It's not a deal-breaker, but it looks like you're already instrumenting the code, and so it would be nice to look at code-coverage as well, especially when running tracegl along with a qUnit or something. You also keep track of branches that have been executed, and so branch coverage would be available as well.

[jomnius]

Bump. Was trying to select all from Tracegl UI and paste into text file to do some some very crude profiling with line counting. Copy and paste not allowed. Tried to use the trace.gz file for same, gzip tells file was corrupted == must be some special custom format.

Code coverage and line count profiling are about the same thing, so I'm here supporting this code coverage request. Both would be extremely useful, please consider adding in some future release.

[codegl]

The trace.gz file is not some specific format, somehow i can't get node to finish the file properly when exiting the program. Its a JSON stream and pretty simple format. However, this sounds like a feature that can be added pretty easily. I'm adding it to the feature request list with code-coverage. Its a pretty natural extension of traceGL.

[jomnius]

Ok, would be happy with code-coverage. The bug with corrupt trace.gz is not so important for me, at least not yet :)

[vivin]

Thank you! Looking forward to this, when you have it implemented! :+1: :)

[Kverma517]

Would it be possible to share the format of the trace file. I want understand the structure and draw call graph.