Fix: print ret value on ust_app start/stop error

Signed-off-by: David Goulet <dgoulet@efficios.com>

diff --git a/src/bin/lttng-sessiond/ust-app.c b/src/bin/lttng-sessiond/ust-app.c
index 0b32f351814bf723710105550b6bd5b1f569501a..98ea50fdb250a6f0f89b2c73240eb7dea4df05d9 100644 (file)
--- a/src/bin/lttng-sessiond/ust-app.c
+++ b/src/bin/lttng-sessiond/ust-app.c
@@ -2350,7 +2350,7 @@ skip_setup:
        /* This start the UST tracing */
        ret = ustctl_start_session(app->sock, ua_sess->handle);
        if (ret < 0) {
-               ERR("Error starting tracing for app pid: %d", app->pid);
+               ERR("Error starting tracing for app pid: %d (ret: %d)", app->pid, ret);
                goto error_rcu_unlock;
        }
 
@@ -2411,7 +2411,7 @@ int ust_app_stop_trace(struct ltt_ust_session *usess, struct ust_app *app)
        /* This inhibits UST tracing */
        ret = ustctl_stop_session(app->sock, ua_sess->handle);
        if (ret < 0) {
-               ERR("Error stopping tracing for app pid: %d", app->pid);
+               ERR("Error stopping tracing for app pid: %d (ret: %d)", app->pid, ret);
                goto error_rcu_unlock;
        }