Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
My code is hanging fwrite with the following stack:
libc.so.6.1::___lll_lock_wait
libc.so.6.1::fwrite
This seems to be happening in solaris.
Only incorrect thing which I can think of is that my code may try to do a parallel fclose on the same FILE pointer which is used for doing fwrite. If a parallel fclose happens will it lead to this kind of a stack?
But, I am not sure if the parallel fclose call really did happen or not?
What could be the problem here?
Looks like something has blown up somewhere. Operations on FILE* normally uses an internal lock to be thread safe. You’ve likely done something to invoke undefned behavior somewhere. E.g. you’ve corrupted the heap, overwriting something important(like a FILE), or the FILE* has been closed – in which case you can’t rely on anything sane to happen if you continue to use it.