On 13/10/2026 17:40, Bruno Haible via GNU coreutils General Discussion wrote:
Hi,
The misc/exec-bad-unicode test that was added on 2026-10-04 fails in an
environment with clang + UBSAN + ASAN.
FAIL: tests/misc/exec-bad-unicode
=================================
+ read executor
+ LC_ALL=C
+ stdbuf -oL $'./\377|\355\272\255|\\u0089|\355\246\277\355\277\277'
$'\377|\355\272\255|\\u0089|\355\246\277\355\277\277'
+ test 127 = 0
+ case "$executor" in
+ false
+ cat err
/bin/bash: symbol lookup error:
/home/runner/work/ci-check/ci-check/coreutils-2026-10-13/build/src/libstdbuf.so:
undefined symbol: __asan_option_detect_stack_use_after_return
+ fail=1
This is obviously related to the 'stdbuf' program. But there are surely other
stdbuf tests, that don't fail?? What do they do differently?
tests/misc/stdbuf.sh works because it's running ASAN instrumented binaries in
the coreutils build,
but when libstdbuf.so is built against ASAN but then tries to run non ASAN
instrumented binaries
you get a link error.
The fix would be to do something like:
stdbuf -oL $SHELL -c : || skip_ ...
Alternatively we might exclude libstdbuf.so from sanitizers.
cheers,
Padraig
