From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,LOTS_OF_MONEY autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,a013984d694d635f X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-04-24 17:21:26 PST Path: newsfeed.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news.stealth.net!news-east.rr.com!news.rr.com!chnws02.mediaone.net!chnws06.ne.mediaone.net!24.91.0.34!typhoon.ne.mediaone.net.POSTED!not-for-mail From: "Jeff Creem" Newsgroups: comp.lang.ada References: <%a0F6.96$284.2129@newsfeed.slurp.net> <9c3vp5$f2s4@cui1.lmms.lmco.com> Subject: Re: VxWorks memory error when closing ADA file X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: <%LoF6.21500$bA2.5861739@typhoon.ne.mediaone.net> Date: Wed, 25 Apr 2001 00:21:15 GMT NNTP-Posting-Host: 24.147.67.93 X-Complaints-To: abuse@mediaone.net X-Trace: typhoon.ne.mediaone.net 988158075 24.147.67.93 (Tue, 24 Apr 2001 20:21:15 EDT) NNTP-Posting-Date: Tue, 24 Apr 2001 20:21:15 EDT Organization: Road Runner Xref: newsfeed.google.com comp.lang.ada:6905 Date: 2001-04-25T00:21:15+00:00 List-Id: "Smark" wrote in message news:9c3vp5$f2s4@cui1.lmms.lmco.com... > "Jeff Creem" wrote in message > news:Wv2F6.20517$bA2.5461988@typhoon.ne.mediaone.net... > > > > vxWorks version? who's compiler? target type? host type? These might help... > > > > Some notes: > > > > On vxWorks, if your file access is via FTP (unless you have a local disk or > > have > > specifically tried to make it via NFS it is probably via FTP). If it is ftp, > > the file is not written to > > the network until the file is closed. > > In fact, the same is true for file access via NFS. > > Mark > In fact unless they broke this for more recent versions of vxWorks, NFS did not cache the entire file in RAM prior to flushing it to the network nor does it read the entire file into RAM prior to allowing read calls to operate. If this is happening with your target I suspect a configuration problem. Now, as for the original question I still wonder if perhaps the filesystem is double mounted (very typical if NFS is used that the device would be accessible both via FTP and NFS and just accessing the file via a different path would change the approach). While it is always possible you have some RAM problem a much more likely event would be some sort of memory allocation/deallocation problem. Are you running with Ada checks enabled? Other than vxWorks is there any C code that is running?