[Zlib-devel] zlib 1.2.2.3 available for testing

[Mark Adler]

On May 30, 2005, at 9:12 AM, Nelson H. F. Beebe wrote:
> That single failure was DEC Alpha OSF/1 4.0 compiled with native cc: 
> the zlib test died with a "Memory fault"
...
> zlib version 1.2.2.3 = 0x1223, compile flags = 0x30000a9
...
> signal Segmentation fault at >*[strlen, 0x3ff801a2ce0]  ldq_u   r1, 
> 0(r16)
> (dbx) where
>>  0 strlen(0x0, 0x0, 0x0, 0x0, 0x0) [0x3ff801a2ce0]
>    1 _doprnt(0x0, 0x0, 0x0, 0x0, 0x0) [0x3ff800ddcc8]
>    2 sprintf(0x11fffd640, 0x140002308, 0x40002310, 0x6c6c6568, 0x7fff) 
> [0x3ff800da08c]

The compile flags tell me that sprintf() returns a value, which should 
be the length of the resulting string.  (Those compile flags are 
useful!)  A strlen() being called within sprintf(), possilbly to 
determine that  length, never finds a terminating zero and goes 
charging off into la la land.  Sounds like a library bug to me.

> However zlib-1.2.2 and earlier passed
> their tests on this system with native cc, so further analysis is
> desirable.

I can see no changes between 1.2.2 and 1.2.2.3 relevant to this issue.  
Perhaps a different *printf function was being used.  What were the 
compile flags for the successful 1.2.2 test?

mark