Re: [tracecompass-dev] Parsing non standard data

[Matthew Khouzam <matthew.khouzam@xxxxxxxxxxxx>]

Oh Oh! this one I can answer.

The data is an byte[]

This is not a type that can be easily extracted into other information.
If you have tracecompass compiled, I suggest you use an ITmfAspect to
extract the pertinent data. If not, I suggest waiting until byte
manipulation comes to xml, which would be soon I think, a masters
student is working on it.

I can whip you up a patch if you want help on that, I don't expect it to
get mainline, but you can have _your_ version of tracecompass that
supports that feature.


On 17-08-02 10:37 AM, Konrad Kokosa wrote:
>
> Hi,
>
>  
>
> I am trying to make XML views for LTTng from CoreCLR. While for most
> events payload is being loaded correctly, some seems to have unparsed
> data. For example, DotNETRuntime:GCGenerationRange have Contents with
> all fields parsed:
>
>  
>
> Timestamp         Channel               CPU       Event type         
> Contents             Binary Location Function Location           
> Source Location
>
> 10:35:41.990 062 403    channel0_0        0            
> DotNETRuntime:GCGenerationRange    Generation=2,
> RangeStart=140491869908992, RangeUsedLength=24,
> RangeReservedLength=24, ClrInstanceID=0, context._vpid=39237,
> context._vtid=39254,
> context._procname=dotnet                                            
>                                
>
> So I am able to draw XML XY chart based on, for example, RangeUsedLength.
>
>  
>
> But for some events there are only unparsed, __data related fields:
>
>  
>
> Timestamp         Channel               CPU       Event type         
> Contents             Binary Location Function Location           
> Source Location
>
> 10:35:41.990 066 003    channel0_0        0            
> DotNETRuntime:GCHeapStats_V1           length=94, ___data___length=94,
> __data__=[120, 136, 28, 0, 0, 0, 0, 0, 176, 254, 16, 0, 0, 0, 0, 0,
> 240, 10, 17, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 24, 0, 0, 0, 0, 0,
> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
> 0, 0, 0, 242, 91, 1, 0, 0, 0, 0, 0, 39, 1, 0, 0, 0, 0, 0, 0, 3, 0, 0,
> 0, 11, 0, 0, 0, 165, 0, 0, 0, 0, 0], context._vpid=39237,
> context._vtid=39254,
> context._procname=dotnet                                     
>
> I know LTTng USG Trace parsing is used here but I am not sure if it is
> possible to extend it somehow to get very valuable fields hidden in
> __data__ field?
>
>  
>
> Konrad Kokosa
>
>
>
> _______________________________________________
> tracecompass-dev mailing list
> tracecompass-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/tracecompass-dev