Re: VxWorks memory error when closing ADA file

["Jeff Creem" <jeff@thecreems.com>]

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..

<jhuber@ellsworth.nlxcorp.com> 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?