assert fail of caget under msvc 8

This appears to be related to this line in caget/caput/camonitor/cainfo.

    setvbuf(stdout,NULL,_IOLBF,0); /* Set stdout to line buffering */

Apparently the new ms CRTL assert fails 2 <= size <= INT_MAX. Thats a new feature of visual C++ 2005 (see <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_setvbuf.asp">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_setvbuf.asp</a>). This does not match POSIX (see <a href="http://www.opengroup.org/onlinepubs/007908799/xsh/setvbuf.html">http://www.opengroup.org/onlinepubs/007908799/xsh/setvbuf.html</a>).

I did find that making this change appears to fix the problem.

    setvbuf(stdout,NULL,_IOLBF,2); /* Set stdout to line buffering */

Jeff

> -----Original Message-----
> From: guobao shen
> Sent: Wednesday, November 23, 2005 5:09 AM
> To: 'Jeff Hill'; 'Vladimir Sirotenko'; <email address hidden>
> Subject: RE: EPICS base compiling using Visual C++ 2005 Express
>
> Dear Dr. Jeff and Dr. Vladimir,
>
> Thank you very much.
>
> I succeeded in the compilation after removing the TD from the fdopen
> specification.
> If I tried to build static libraries, there was no problem. But if I tried
> to build shared
> libraried, I must copy the manifest specification file for each exe or dll
> file into
> bin/win32-x86 manually.
>
> I also found that I can not execute the catools such as
> caget/cainfo/camonitor correctly.
> The only error message is "caget.exe has encountered a problem and needs
> to
> close."
>
> Can you give any suggestion?
>
> Thanks again.
>
> Best Regards,
>
> Guobao Shen
> J-PARC Control Group
>
>
> >
> > I looked into this "w+bTD" verses "W+B".
> >
> > The purpose of this code is to open an identical type of
> > temporary file on all OS. This particular problem is, of
> > course, in Microsoft specific code working with previous
> > versions, but not with Visual C++ 2005.
> >
> > The very latest documentation at MS with a 2005 time stamp on
> > it lists "T"
> > and "D" as valid Microsoft specific options to _fdopen. This
> > therefore smells like a bug at MS. Nevertheless, the proposed
> > change appears to work - not creating any permanent files on
> > the disk. This is probably because roughly equivalent options
> > are specified to the preceding open().
> >
> > We have committed the suggested change - ETA R3.14.8.
> >
> > Jeff
> >
> > > -----Original Message-----
> > > From: Vladimir Sirotenko
> > > Sent: Tuesday, November 22, 2005 9:34 AM
> > > To: guobao shen; <email address hidden>
> > > Subject: Re: EPICS base compiling using Visual C++ 2005 Express
> > >
> > > Try to do the following, it worked for us:
> > >
> > > Antelope failed to run correctly because it could not create a
> > > temporary file.
> > > Modify srclibComosiWIN32epicsTempFile.cpp and remove
> > the TD from
> > > the fdopen specification.
> > >
> > > pNewFile = _fdopen ( fd, "w+b" ); instead of pNewFile =
> > > _fdopen ( fd, "w+bTD" );
> > >
> > > Vladimir
> > >

Original Mantis Bug: mantis-230
    http://www.aps.anl.gov/epics/mantis/view_bug_page.php?f_id=230