Clarify clock correlation error message
authorMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Tue, 6 Mar 2012 23:04:47 +0000 (18:04 -0500)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Tue, 6 Mar 2012 23:04:47 +0000 (18:04 -0500)
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
lib/trace-collection.c

index 0ee3c29f08fcb81ad213f4a349e3d4ec18196ce9..42d809623d419d22d2df194fe88e45c92ae6592b 100644 (file)
@@ -157,7 +157,7 @@ int trace_collection_add(struct trace_collection *tc,
                                check_clock_match,
                                &clock_match);
                if (!clock_match.clock_match) {
-                       fprintf(stderr, "[error] No clocks can be correlated and multiple traces are added to the collection.\n");
+                       fprintf(stderr, "[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\".\n");
                        goto error;
                }
        }
This page took 0.032823 seconds and 4 git commands to generate.