Changing a string-based expression's length will break listing on Big Endian hosts as the exported data is padded "on the wrong end". Since not adjusting the length seems not to cause any problems, just drop it instead of trying to fix it. Signed-off-by: Phil Sutter --- src/segtree.c | 1 - 1 file changed, 1 deletion(-) diff --git a/src/segtree.c b/src/segtree.c index ab107493ea97b..7d4c50f499ef7 100644 --- a/src/segtree.c +++ b/src/segtree.c @@ -413,7 +413,6 @@ void concat_range_aggregate(struct expr *set) tmp = constant_expr_alloc(&r1->location, r1->dtype, BYTEORDER_BIG_ENDIAN, (str_len + 1) * BITS_PER_BYTE, data); - tmp->len = r2->len; list_replace(&r2->list, &tmp->list); r2_next = tmp->list.next; expr_free(r2); -- 2.51.0