[bug-libunistring] [bug #54453] abort in u8_possible_linebreaks in libunistring 0.9.10

[Natanael Copa]

Follow-up Comment #6, bug #54453 (project libunistring):

The binaries comes from official Alpine Linux x86_64 builder:
http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/

I build them locally with debugging symbols to be able to provide backtraces.

Alpine Linux edge(rolling release) x86_64.

$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-alpine-linux-musl/6.4.0/lto-wrapper
Target: x86_64-alpine-linux-musl
Configured with: /home/buildozer/aports/main/gcc/src/gcc-6.4.0/configure
--prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info
--build=x86_64-alpine-linux-musl --host=x86_64-alpine-linux-musl
--target=x86_64-alpine-linux-musl --with-pkgversion='Alpine 6.4.0'
--enable-checking=release --disable-fixed-point --disable-libstdcxx-pch
--disable-multilib --disable-nls --disable-werror --disable-symvers
--enable-__cxa_atexit --enable-default-pie --enable-cloog-backend
--enable-languages=c,c++,objc,java,fortran,ada --disable-libssp
--disable-libmpx --disable-libmudflap --disable-libsanitizer --enable-shared
--enable-threads --enable-tls --with-system-zlib --with-linker-hash-style=gnu
Thread model: posix
gcc version 6.4.0 (Alpine 6.4.0) 


musl libc 1.1.19 + some backported patches.

Same toolchain for both 0.9.9 and 0.9.10. It only happens with 0.9.10.

What is somewhat weird is that a couple of times when I have built
libunistring with -g, the problem no longer manifests itself. When it does,
the gettext have exactly 21 failing test in testsuite.

It is quite possible that this is a memory corruption or undefined behavior
somewhere else, in either gettext, libunistring or gnulib, but I have no clue
where the problem may be.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?54453>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/