|Re: [tracecompass-dev] Issue with custom Tracer based on Trace compass|
I updated our application to the last version of Trace Compass (5.3), and the issue is still there, but from now on I would be able to test patches.
So babeltrace detects it as a malformed trace? What is the exact output of babeltrace? Maybe it's simply something that we did not implement in Trace Compass yet.
Would you be allowed to share the trace with us?
On 3/31/20 10:00 AM, tracecompass developer discussions wrote:
For now, you can first read the trace with babeltrace to make sure it is ok. But Trace Compass should be able to figure out. I'll try to fix the dealock you mention at least, thanks for providing the stack trace, I'll see what can easily be done. Can you test patches (ie running from Trace Compass sources) or do use one of the Trace Compass RCP? If so, which version of Trace Compass are you using? In any case, have you tried the latest version (5.3) to make sure the bug is still present?
Back to the top