Login
Templates, Tools and Utilities
for Clarion Developers
Templates, Tools and Utilities
|
||
|
|
|
Add a comment to an Icetips ArticlePlease add your comments to this article.
Please note that you must provide both a name and a valid email address in order
for us to publish your comment. Comments are moderated and are not visible until they have been approved. Spam is never approved!
Back to article list Search Articles Add Comment Printer friendly Direct link ABC: Finding places where files are closed without calling the close method (C5) 1999-12-23 -- Scott Ferrett Newsgroups: topspeed.products.c5ee
> There were lots of problems with "File Not
> Open" and there was no way we could find the missing closes.
I had an idea last night that will allow you to easily find these bugs
if you get future clients needing it tracked.
In abfile.clw add code add this just before the CLOSE call
SELF.File{PROP:Log} = 'In ABFILE'
Run the program with profiling on. Once you get the file not open
error, close the file and search the log for CLOSE calls. At least one
will not be preceded with In ABFILE. That is the one being caused by
the thread terminating without fm.close being called. You can then
look at the calls before to work out the bit of code that is missing
the call.
SuRF
Today is November 21, 2024, 6:28 am This article has been viewed 35382 times. Google search has resulted in one hit on this article since January 25, 2004.
|
|