Fix: src.text.details: use write_uint_prop_value to handle unsigned values in write_i...
authorSimon Marchi <simon.marchi@efficios.com>
Sat, 5 Mar 2022 01:20:34 +0000 (20:20 -0500)
committerPhilippe Proulx <eeppeliteloop@gmail.com>
Tue, 8 Mar 2022 17:46:00 +0000 (12:46 -0500)
commit3feba3d89aecffdf8c3f4edad75275d44b38f156
tree5e71a53e02da7cc661c21ba3268cb0928051e3e7
parent78169723129e666342d1dd5bc6194f80d70fe862
Fix: src.text.details: use write_uint_prop_value to handle unsigned values in write_int_range

I tried creating an option field class with unsigned integer selector,
with a [1, UINT64_MAX] range.  The details field class shows it as:

     opt_with_uint_sel: Option (unsigned integer selector) (Selector field location [Event payload: uint_selector]):
      Selector ranges: [1, -1]

The -1 is wrong.  Fix two spots to call write_uint_prop_value instead of
write_int_prop_value.

After:

    opt_with_uint_sel: Option (unsigned integer selector) (Selector field location [Event payload: uint_selector]):
       Selector ranges: [1, 18,446,744,073,709,551,615]

Change-Id: I83344b2a241f597da86c21da030b40eed2a4955f
Signed-off-by: Simon Marchi <simon.marchi@efficios.com>
Reviewed-on: https://review.lttng.org/c/babeltrace/+/7503
CI-Build: Philippe Proulx <eeppeliteloop@gmail.com>
Tested-by: jenkins <jenkins@lttng.org>
Reviewed-by: Philippe Proulx <eeppeliteloop@gmail.com>
src/plugins/text/details/write.c
This page took 0.024943 seconds and 4 git commands to generate.