hello. my program hangs inside an fprintf. debugger follows it to procedure _lock_file where it never escapes from. i believe the final executed command is EnterCriticalSection( &(((_FILEX *)pf)->lock) );
anyone know why this is happening? the filepath associated with the file pointer seems valid and i didnt get any error messages opening the file. thank you for your time.
Well you didn't mention which OS/Compiler you're using.
Nor did you post a simple program which demonstrates the fault.
Nor did you mention for example whether you were using threads in your program.
Two scenarios,
1. Your code is full of bugs, and it's managed to trash the library data structures into thinking there is a file lock, when there isn't.
2. You've mixed thread-safe and non thread-safe code in a threaded program, and the collective mis-understanding is what you're seeing.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
fprintf is thread safe, so it enters a critical section whenever you try to write to a file.
So if another thread is trying to write to the same file and somehow hangs/fails/takes time, your thread will be blocked until the other thread is finished.
So as Salem mentions, show some code to illustrate the problem.
Originally Posted by Adak
thank you for your time. no threads here so i understand therefor it must be a bug as you say. i'm bubblesorting arrays of structs of files pointers numerous times so i must have damaged a file pointer somewhere. you've helped me and i appreciate it. thank you.
