|Re: [tracecompass-dev] Question about creating XML stateProvider for custom trace format|
Thanks for your quick responses, I have used the patch linked by Geneviève and have changed my stateProvider accordingly.
It works perfectly and is exactly what I was trying to achieve.
Also, the traceType attribute now works correctly using the custom.txt.trace:<category>:<parserName> format (I had previously only managed to get my view visible by leaving the traceType attribute out)
Van: tracecompass-dev-bounces@xxxxxxxxxxx <tracecompass-dev-bounces@xxxxxxxxxxx> namens Bernd Hufmann <bernd.hufmann@xxxxxxxxxxxx>
Verzonden: donderdag 2 juni 2016 15:11:26
Onderwerp: Re: [tracecompass-dev] Question about creating XML stateProvider for custom trace format
Thanks for the interest in Trace Compass.
It is possible to create a XML analysis using custom text traces. There are a view things you need to know which are not obvious.
- the <traceType> attribute is: custom.txt.trace:<category>:<parserName>
where <category> is the category that you specified in the custom text parser
<parser name> is the custom parser name
- the eventName is the same for all events and it is the custom parser name <parserName> from above. So for the state changes in the state provider you need work with the event fields. The event field names in custom parsers are the column names. (BTW, different event names is currently discussed as Genevieve pointed out in her answer)
I've done this for traces generated by Trace Compass when enabling the debug information. I've attached a tar file with the custom parser, the state provider and an example trace. Please have look and take it as a reference for your state provider. If you want to try it, import the custom parser (TmfRequest-saved.xml), then import the state provider (TmfRequestState.xml) and finally open trace TmfTraceRequest.log. Open the XML view as usual.
Please let us know how it goes.
On 06/02/2016 08:08 AM, Robbert Jongeling wrote:
Back to the top