Hi Bruno, * Bruno Haible wrote on Sun, Apr 26, 2009 at 12:27:44PM CEST: > Unit tests revealed that some Unicode string functions were dependent on > the result of malloc(0). This fixes it, and documents the portability problem.
This looks fishy. AC_FUNC_MALLOC should define malloc to rpl_malloc and the code from the malloc module should be used and fix this issue, no? Cheers, Ralf > 2009-04-26 Bruno Haible <[email protected]> > > Avoid test failures on AIX and OSF/1. > * lib/uniconv/u8-conv-from-enc.c (u8_conv_from_encoding): Avoid calling > malloc(0). > * lib/uniconv/u8-conv-to-enc.c (u8_conv_to_encoding): Likewise. > * lib/unilbrk/ulc-possible-linebreaks.c (ulc_possible_linebreaks): > Likewise. > * lib/unilbrk/ulc-width-linebreaks.c (ulc_width_linebreaks): Likewise. > * lib/uniwbrk/ulc-wordbreaks.c (ulc_wordbreaks): Likewise. > * lib/uniconv/u-conv-to-enc.h (FUNC): Likewise. Fix memory leak. > * lib/unistr/u-cpy-alloc.h (FUNC): Call malloc(1) instead of malloc(0). > * doc/posix-functions/malloc.texi: Document the portability problem > related to malloc(0).
