Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!decvax!eagle_snax!hinode!geoff
From: geoff@hinode.east.sun.com (Geoff Arnold)
Newsgroups: comp.sys.ibm.pc
Subject: Re: How to determine the filenames of open files
Keywords: fopen fclose fname?
Message-ID: <508@eagle_snax.UUCP>
Date: 4 Apr 89 18:12:08 GMT
References: <408@focsys.UUCP>
Sender: news@eagle_snax.UUCP
Reply-To: garnold@sun.COM (Geoff Arnold)
Distribution: na
Organization: Sun Microsystems, Billerica MA
Lines: 30

In article <408@focsys.UUCP> larry@focsys.UUCP (Larry Williamson) writes:
>Is there someway I can determine the filenames of all the currently
>open files?
>[...]
>We cannot track down any place where we open a file and don't close
>it, so we are beginning to suspect the other library routines. One
>of them is possibly not closing some temp file. But who?
>
>Any suggestions?
>
>Thanks,
>  -Larry.
>-- 
>Larry Williamson  -- Focus Systems -- Waterloo, Ontario
>                  watmath!focsys!larry  (519) 746-4918

It looks like you are without one of the most essential of all
DOS developer's tools: PCWATCH. This is an IBM product (from their
Pesonally Developed Software series, though I believe they
may have sold the reseller rights to someone else recently),
which allows you to monitor selected DOS system calls. If your
application uses full screen graphics, not to worry: you can
drop an MDA into the PC, hook up a monochrome monitor and redirect the
output to that. It's quite invaluable.

Geoff
Geoff Arnold,                              Internet: garnold@sun.com
Manager, PC-NFS Engineering                UUCP: ....!sun!garnold
PCDS Group, Sun Microsystems Inc.
*** I SPEAK ONLY FOR MYSELF *** (MY CHILDREN INSISTED THAT I SAY THAT) ***