keeping FILE* object open

I use visual studio and standard C for programming. The program I am writing uses winsock, too. I used to open file with fopen "w", but the program encounters exception if I open file and use fprintf or fclose after the long time waiting for socket. This exception doesn't happen if I open file and immidiately write and close (fopen,fprintf,fclose sequentially).

Why?


Thanks!

Do you have software that closes open sockets after a certain length of time, if they're not being used? I'm thinking of firewall type programs, in your operating system.

Originally Posted by Adak

Do you have software that closes open sockets after a certain length of time, if they're not being used? I'm thinking of firewall type programs, in your operating system.

I've no problem in socket itself, it works just fine. I've problem in FILE operation that has no relation with socket. FILE stays open for a nearly long time only.

Thanks!

Are you sure you're using it correctly, and are you sure they are what's causing the problem (and not something else)? There are a few things you ought to look out for:

— Check the return value of fopen.
— Ensure that you're passing the correct arguments to those functions.

If you're logging data to a file infrequently, then it might be beneficial to only open the file (in append mode) when you need to log data, and close it immediately after. I don't really see how having an opened file could be a problem, since stdin, stdout, and stderr are typically open for your entire program's interpretation unless you close them manually. You aren't using winsock functions with FILE objects, are you?

> but the program encounters exception if I open file and use fprintf or fclose after the long time waiting for socket.
Have you considered FINDING the bug in your present system, rather than trying to find an alternative solution (which may still have the bug) which doesn't exhibit the problem.

Run the debug build in the debugger, and just wait for it to crash. It will point you at the location where it crashed (you might have to traverse the call stack to locate the caller in your code), but at least it will give you some ideas to think about.

You've got a bug with a repeatable cause - be thankful for small mercies.

What really irritates people who code for a living are bugs with no repeatable cause at all.

Originally Posted by Barney McGrew

Are you sure you're using it correctly, and are you sure they are what's causing the problem (and not something else)? There are a few things you ought to look out for:

— Check the return value of fopen.
— Ensure that you're passing the correct arguments to those functions.

If you're logging data to a file infrequently, then it might be beneficial to only open the file (in append mode) when you need to log data, and close it immediately after. I don't really see how having an opened file could be a problem, since stdin, stdout, and stderr are typically open for your entire program's interpretation unless you close them manually. You aren't using winsock functions with FILE objects, are you?

The error doesn't persist. I guess it was some problem resolved by restarting. Maybe...


Thanks!