libbabeltrace does not complains if it cannot correlate two traces
We have two different traces. When we open them with babeltrace, it
complains that it cannot correlate the traces timestamps and stop.
When we open them with libbabeltrace, they open without warnings but the
timestamps are erroneous.
Updated by Julien Desfossez about 8 years ago
- Status changed from New to Feedback
- Assignee set to Julien Desfossez
- Target version set to Babeltrace 1.0
I don't see the problem.
With the API adding two traces with a different clocks, I get the following message and the return code is negative as expected :
[error] No clocks can be correlated and multiple traces are added to the collection. If you are certain those traces can be correlated, try using "--clock-force-correlate".
[error] Opening the trace
Can you provide a way to reproduce the problem ?