Mail Archives: djgpp/2001/10/07/11:04:15
"Orlando P. Hevia" wrote:
>
> > I don't understand: you are supposed to close the file
> > before trying to open unit 52 again. This program doesn't
> > close the file, so it will only be deleted when the
> > program exits. What exactly are you trying to prove?
>
> When you run the program, it aborts because the memory
> access violation (X(N) with N not defined) and you will
> have
> a forta52a file in your tmp directory. The CLOSE (52) line
> is not reached, the file is not correctly closed and it is
> not deleted.
Ah, I see now.
Well, this is a kind of feature: when a program crashes, the part of the
exit code which normally closes and removes scratch files is bypassed. The
reason for this is DOS/Windows tradition, but this is also a valuable
debugging aid: if your program crashes, you might wish to look into any
scratch files it created for clues about the possible reasons for the crash.
If you want to make sure the scratch files are deleted even if the program
aborts, you can install a signal handler for SIGSEGV and make it call
`exit'.
> In some point, the program will abort, but by another
> reason: it cannot open a new scratch file. This is the
> second part (the more important for our users) of the
> problem, that was aborting the Alternative Transients
> Program (ATP).
It is probably a good idea to clean up the temporary directory from time to
time. Since DJGPP uses its own temporary directory, pointed to by TMPDIR,
you could clean it up without worrying about other applications or the OS
itself.
- Raw text -