Hello Eric, On Monday, August 11, 2008 at 20:57:53 -0600, Eric Blake wrote:
> The real problem thus seems to be that the gnulib xvasprintf-posix > module is not working around this bug in your *printf family of > functions. Could you post config.log for more details on what > ./configure determined about printf? Sure. There is a segfault on the test for large precisions, on "%.4000d". On libc5 this format works well until "%.1020d", but segfaults for "%.1021d" and above. A severely trimmed down config.log.gz comes attached. Here is the summary: | checking for vasnprintf... no | checking whether snprintf is declared... yes | checking whether printf supports size specifiers as in C99... no | checking whether printf supports 'long double' arguments... yes | checking whether printf supports infinite 'double' arguments... no | checking whether printf supports infinite 'long double' arguments... no | checking whether printf supports the 'a' and 'A' directives... no | checking whether printf supports the 'F' directive... no | checking whether printf supports the 'n' directive... yes | checking whether printf supports POSIX/XSI format strings with positions... yes | checking whether printf supports the grouping flag... yes | checking whether printf supports the left-adjust flag correctly... yes | checking whether printf supports the zero flag correctly... no | checking whether printf supports large precisions... no | checking whether printf survives out-of-memory conditions... no | checking for snprintf... yes | checking whether snprintf respects a size of 1... no | checking whether _snprintf is declared... no | checking for vasprintf... yes Alain.
config.log.gz
Description: application/gunzip
