`BT_FUNC_STATUS_OVERFLOW` is an error status, so append an error cause
to make details available.
Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
Change-Id: I1524a088698a7b8bf240e8b1206bf06d4b21870f
Reviewed-on: https://review.lttng.org/c/babeltrace/+/1769
Tested-by: jenkins <jenkins@lttng.org>
BT_ASSERT_PRE_DEV_NON_NULL(ns, "Nanoseconds (output)");
ret = bt_util_ns_from_origin_clock_class(clock_class, cycles, ns);
if (ret) {
- ret = BT_FUNC_STATUS_OVERFLOW;
- BT_LIB_LOGD("Cannot convert cycles to nanoseconds "
+ BT_LIB_LOGE_APPEND_CAUSE("Cannot convert cycles to nanoseconds "
"from origin for given clock class: "
"value overflows the signed 64-bit integer range: "
"%![cc-]+K, cycles=%" PRIu64,
clock_class, cycles);
+ ret = BT_FUNC_STATUS_OVERFLOW;
}
return ret;
"Clock snapshot is not set: %!+k", clock_snapshot);
if (clock_snapshot->ns_from_origin_overflows) {
- BT_LIB_LOGD("Clock snapshot, once converted to nanoseconds from origin, "
+ BT_LIB_LOGE_APPEND_CAUSE(
+ "Clock snapshot, once converted to nanoseconds from origin, "
"overflows the signed 64-bit integer range: "
"%![cs-]+k", clock_snapshot);
ret = BT_FUNC_STATUS_OVERFLOW;