Project

General

Profile

Actions
Copy link

Bug #209

closed
YB JD

libbabeltrace does not complains if it cannot correlate two traces

Bug #209: libbabeltrace does not complains if it cannot correlate two traces

Added by Yannick Brosseau over 13 years ago. Updated over 13 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
Julien Desfossez
Category:
-
Target version:
Babeltrace 1.0
Start date:
Due date:
% Done:

0%

Estimated time:

Description

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.

JD Updated by Julien Desfossez over 13 years ago Actions
Copy link
 #1

  • 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 ?

Thanks,

Julien

YB Updated by Yannick Brosseau over 13 years ago Actions
Copy link
 #2

  • Status changed from Feedback to Invalid

I cannot reproduce it.

Actions
Copy link

Also available in: PDF Atom