[Zlib-devel] zlib 1.2.2.3 available for testing: OSF/1 4.0 Alpha failure

Mark Adler madler at alumni.caltech.edu
Mon May 30 18:46:02 EDT 2005


On May 30, 2005, at 2:43 PM, Nelson H. F. Beebe wrote:
> For Mark's personal use, I'll post him a pointer to a tar file with
> the three log files,

Nelson,

Thanks.  Here are the zlib compile flags I was looking for.  The 1.2.2 
run showed:

     zlib version 1.2.2 = 0x1220, compile flags = 0x20000a9

whereas the 1.2.2.3 run showed:

     zlib version 1.2.2.3 = 0x1223, compile flags = 0x30000a9

As I had suspected, they're using different library functions.  The 
0x2... means 1.2.2 used vsprintf(), whereas 0x3... means 1.2.2.3 used 
sprintf().  However I have yet to figure out why they're using 
different functions.  The configure output from 1.2.2 indicates that it 
should have used sprintf().  But it didn't.  Perhaps somehow STDC got 
defined somewhere between the configure run and the compile for 1.2.2, 
which would make it use vsprintf().  1.2.2.3 is consistent in that both 
the configure output and the compile flags indicate the use of 
sprintf().  In any case, it appears that the bug is in sprintf(), or 
somehow in the parameter passing as Markus has suggested.

mark





More information about the Zlib-devel mailing list