muxer: append causes on some _next iterator method code paths
authorSimon Marchi <simon.marchi@efficios.com>
Wed, 13 Nov 2019 19:13:06 +0000 (14:13 -0500)
committerSimon Marchi <simon.marchi@efficios.com>
Fri, 15 Nov 2019 17:58:21 +0000 (12:58 -0500)
commit7fb13d3fb818c75c3cc67f37ce846492dc628a69
tree2c15fa174c30191bbcaca901d7864428591a239d
parent42a6316598eda35c8f23f8afbf579e385dc6de40
muxer: append causes on some _next iterator method code paths

The goal of this patch (on top of the fact that having more error causes
is nice) is to ensure that if an error status is returned to
muxer_msg_iter_do_next, an error is set on the current thread.  This
will help for the next patch, which will save and restore the error in
this function.

Change-Id: I7221af107f330ab5ded10b69f24121be6ad1678c
Signed-off-by: Simon Marchi <simon.marchi@efficios.com>
Reviewed-on: https://review.lttng.org/c/babeltrace/+/2382
Reviewed-by: Francis Deslauriers <francis.deslauriers@efficios.com>
src/plugins/utils/muxer/muxer.c
This page took 0.024582 seconds and 4 git commands to generate.