src.ctf.fs: fix switch cases using wrong enumerator

Fix these two cases using CTF_MSG_ITER_MEDIUM_STATUS_FOO instead of
CTF_MSG_ITER_STATUS_FOO.  This isn't a problem in practice, because they
have the same numerical values.

Change-Id: I5d9e22c4e25e9c28a488c4a7b12bf102208dacf0
Signed-off-by: Simon Marchi <simon.marchi@efficios.com>
Reviewed-on: https://review.lttng.org/c/babeltrace/+/7095
Reviewed-by: Philippe Proulx <eeppeliteloop@gmail.com>

diff --git a/src/plugins/ctf/fs-src/fs.c b/src/plugins/ctf/fs-src/fs.c
index ac3bdb31e73d28002f946e3717fb106105814dfb..f3104b804d64e68a92e3700107b06f320a9ad628 100644 (file)
--- a/src/plugins/ctf/fs-src/fs.c
+++ b/src/plugins/ctf/fs-src/fs.c
@@ -86,13 +86,13 @@ bt_message_iterator_class_next_method_status ctf_fs_iterator_next_one(
                 */
                bt_common_abort();
 
-       case CTF_MSG_ITER_MEDIUM_STATUS_ERROR:
+       case CTF_MSG_ITER_STATUS_ERROR:
                BT_MSG_ITER_LOGE_APPEND_CAUSE(msg_iter_data->self_msg_iter,
                        "Failed to get next message from CTF message iterator.");
                status = BT_MESSAGE_ITERATOR_CLASS_NEXT_METHOD_STATUS_ERROR;
                break;
 
-       case CTF_MSG_ITER_MEDIUM_STATUS_MEMORY_ERROR:
+       case CTF_MSG_ITER_STATUS_MEMORY_ERROR:
                BT_MSG_ITER_LOGE_APPEND_CAUSE(msg_iter_data->self_msg_iter,
                        "Failed to get next message from CTF message iterator.");
                status = BT_MESSAGE_ITERATOR_CLASS_NEXT_METHOD_STATUS_MEMORY_ERROR;