[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::decc

Title:DECC
Notice:General DEC C discussions
Moderator:TLE::D_SMITHNTE
Created:Fri Nov 13 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2212
Total number of notes:11045

2192.0. "Can you identify this image identification?" by STAR::SWEENEY () Fri May 16 1997 16:14

Hi,

I have a customer who is running an OpenVMS VAX V6.1 system with the 
DECC$SHR image listed below.  

        Image Identification Information

                image name: "DECC$SHR"
                image file identification: "V06.0-64"
                link date/time: 11-APR-1995 12:10:20.12
                linker identification: "05-13"

I have been unable to determine the source of this image as it is not in any of
the DEC C remedial kits currently on disk, nor is it the V6.1 vanilla image.

This customer is encountering a problem with DCE on OpenVMS that is quite
similar to  a previously reported problem, case CFS.40218, from BC Systems. 
This previous problem was due to lseek() not positioning to the end of file
correctly. This case does not mention what DEC C kit introduced the problem. 
The image ident for the buggy shareable image is not listed in the case.  My
customer claims DEC C was upgraded on all his systems and he still has the DCE
problem. So... 

Can someone indicate whether the image listed above has an lseek problem?
Given the image ident info, this certainly does not look like the shareable
image was updated from a recent DEC C kit as the customer claims.  

Dave


T.RTitleUserPersonal
Name
DateLines
2192.1Visit CRTL home pageTLE::BORISBoris Gubenko, DEC C RTLFri May 16 1997 20:0525
  Unfortunately, I also cannot determine the source of the image, but
  DECC$SHR.EXE is not shipped with the compiler. It is shipped with VMS
  itself, so upgrading DEC C does not help.

  Check "Reported Problems Cross Reference Table" on the DEC C RTL home page:

	http://hndymn.zko.dec.com/~crtl

  for availability of ECO kits for V6.1.

  Hopefully, your customer's problem is addressed in VAXACRT07_061 (VAX)
  and ALPACRT09_061 (Alpha) kits for V6.1.

  From Release Notes:

      o  The lseek function may  position  incorrectly  when  given  the
         SEEK_END  option.   Typically  this  occurs  when  the internal
         buffer is full and the last operation done to the file is flush
         or sync.

  Have the customer install this kit(s) and let us know if the problem goes
  away.

  Boris
2192.2TLE::D_SMITHDuane Smith -- DEC C RTLTue May 20 1997 12:271
    The image in .0 is from the VAXACRT02_061 ECO kit.