[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Asan testing of IDN

From: Jeffrey Walton
Subject: Asan testing of IDN
Date: Mon, 13 May 2019 15:37:04 -0400

Hi Everyone,

I'm catching some failed self tests during IDN testing with Asan. The
first two tests runners are OK. The third runner fails as shown below.

When I check tests/test-suite.log I see:

FAIL: tst_stringprep

==3648==ASan runtime does not come first in initial library list; you
should either link runtime to your application or manually preload it
FAIL tst_stringprep (exit status: 1) looks OK:

$ ldd libidn-1.35/lib/.libs/ (0x00007ffdbda7d000) => /lib64/ (0x00007f25b7a04000)

The third test runner uses -fsanitize=address as requested. I
inspected all messages with 'libtool: link:', and they look OK. All
links that produce artifacts use the sanitizer option. I did not see
use of LD_PRELOAD, so I don't believe it is causing the error.

Why is the third test runner failing?


# Tail of third runner build
/bin/sh ../libtool  --tag=CC   --mode=link gcc   -g2 -O2
-fsanitize=address -fno-omit-frame-pointer -march=native -fPIC
-pthread -no-install -L/var/sanitize/lib64 -fsanitize=address
-Wl,-R,/var/sanitize/lib64 -Wl,--enable-new-dtags -o tst_tld tst_tld.o
libutils.a ../lib/ ../gl/ -ldl -lpthread
libtool: link: gcc -g2 -O2 -fsanitize=address -fno-omit-frame-pointer
-march=native -fPIC -pthread -fsanitize=address -Wl,-R
-Wl,/var/sanitize/lib64 -Wl,--enable-new-dtags -o tst_tld tst_tld.o
-Wl,--no-as-needed  -L/var/sanitize/lib64 libutils.a
../lib/.libs/ ../gl/.libs/libgnu.a -ldl -lpthread -pthread
-Wl,-rpath -Wl,/home/build/libidn-1.35/lib/.libs -Wl,-rpath
gmake[2]: Leaving directory '/home/build/libidn-1.35/tests'
gmake  check-TESTS
gmake[2]: Entering directory '/home/build/libidn-1.35/tests'
gmake[3]: Entering directory '/home/build/libidn-1.35/tests'
FAIL: tst_stringprep
FAIL: tst_punycode
FAIL: tst_idna
FAIL: tst_idna2
FAIL: tst_idna3
FAIL: tst_idna4
FAIL: tst_nfkc
FAIL: tst_pr29
FAIL: tst_strerror
FAIL: tst_toutf8
FAIL: tst_symbols
FAIL: tst_badutf8
FAIL: tst_utf8crash
FAIL: tst_toascii64oob
FAIL: tst_badutf8nfkc
FAIL: tst_tld

reply via email to

[Prev in Thread] Current Thread [Next in Thread]