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-23 16:02:24 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> 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: Date: Mon, 23 Apr 2001 23:02:14 GMT NNTP-Posting-Host: 24.147.67.93 X-Complaints-To: abuse@mediaone.net X-Trace: typhoon.ne.mediaone.net 988066934 24.147.67.93 (Mon, 23 Apr 2001 19:02:14 EDT) NNTP-Posting-Date: Mon, 23 Apr 2001 19:02:14 EDT Organization: Road Runner Xref: newsfeed.google.com comp.lang.ada:6870 Date: 2001-04-23T23:02:14+00:00 List-Id: 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. This means that the entire file stays resident in RAM until the close call is made. Perhaps if this is a large file you are running out of memory. If you can, do some memShow commands at the shell while the file is being written to before it closes. Beyond that it is hard to say without more details since many of us have used vxWorks and Ada to create files before with no problems. You could of course set a breakpoint at the close and then step into the OS code to get a better idea.. wrote in message news:%a0F6.96$284.2129@newsfeed.slurp.net... > I am running an ADA build in a VxWorks OS. When > I close one of my log files, the OS states that > there is a memory deallocation error. However, > the data is saved to the log file and the file > closes without any ADA errors or exceptions. > Moreover, the code to close the file is just: > > ADA.TEXT_IO.CLOSE(ERROR_FILE); > > Finally, I use the same procedure in other log > files without any errors. > > So, is there an alternative method I could try? > Or possibly a way to debug this error in ADA?