On Sat, 9 Mar 2019 at 06:10, Jeffrey Walton <noloader@xxxxxxxxx> wrote: > > I'm building libunistring on Fedora 29 with GCC 8.3. > -fsanitize=address was added to CFLAGS and LDFLAGS. Link is drive > through GCC, and I see the flag is present: > > /bin/sh ../libtool --tag=CC --mode=link gcc -g2 -O2 > -fsanitize=address -march=native -fPIC -no-undefined -version-info > 3:0:1 ... -o libunistring.la ... -ldl -lpthread That's the libtool library file, not the libunistring.so.2 library. Is the -fsanitize=address option used when creating the actual library? > The library's self tests fail at runtime: > > gmake: symbol lookup error: lib/.libs/libunistring.so.2: undefined symbol: > __asan_option_detect_stack_use_after_return Presumably ldd will show that library isn't actually linked to libasan, so it doesn't matter if it's installed or not. > libasan is installed: > > $ sudo dnf install libasan > Package libasan-8.3.1-2.fc29.x86_64 is already installed. > > UBsan is handled properly by GCC. > > Any ideas why GCC is not linking Asan libraries? > > Thanks in advance.
