sherman%v70nl.DECnet@NUSC.ARPA ("V70NL::SHERMAN") (06/26/87)
C 2.2-015 still bombs out with that long format. Any news from you folks with 2.3? Bill. ------
oberman%icaen.DECnet@LLL-ICDC.ARPA ("ICAEN::OBERMAN") (06/28/87)
>C 2.2-015 still bombs out with that long format. Any news from you folks with >2.3? I'm pretty sure the printf function is in the VAXCRTL. So the C version shouldn't effect it. I think you will have to wait for VMS V4.6. R. Kevin Oberman Lawrence Livermore National Laboratory arpa: oberman@lll-icdc.arpa (415) 422-6955 Disclaimer: Neither my employer nor myself can take resposibility for the accuracy of this information. I believe it is correct, but if it's not I can only say "Sorry". I'm a rotten typist and a worse speller, so forgive any silly errors. ------
joey@tessi.UUCP (Joe Pruett) (06/29/87)
We have seen printf causing access violations if the resultant string is > 512, no matter what. It's not the format string that's causing the problem, but the size of all the data that will be generated. Sounds like an array of 512 on the stack that trashes your return values. We were printing out long lines of 1's and were seeing access violations for address 31313131 (hex 31 is ascii '1'). We run C 2.3 and VMS 4.4. Joe Pruett Test Systems Strategies ...!tektronix!tessi!joey