Thread: fprintf() causes core dump when executed in certain sections of code

I use fprintf() calls throughout a particular function. Most of them cause no problems & behave as expected. However, I've just added a conditional statement within this function, and any fprintf() statement I attempt to execute within this conditional statement, causes a core dump when the code runs.

I've verified that the values & the file pointers within this new conditional statement are all valid. I don't use fclose() on any file pointers until after this condition executes. Any thoughts about what might result in fprintf() calls in only one particular section in the middle of my code, to fail?

Thanks for your input.

In case it's useful: the new conditional statement that's causing problems, was copied verbatim from an earlier code version that ran perfectly. I was careful to declare all variables & file pointers used in this conditional, within my new code. But, although the fprintf() calls worked fine in my previous code, now they're causing a problem...

The file pointer is invalid? Who knows without seeing code? Try running it in the debugger.

No, as I mentioned, the file pointers that I've tried are all valid (i.e. they can all be used successfully before & after this new conditional, but not within it). But thanks for the suggestion.

You were right, rags... I had missed that fclose() was being called and *then* the conditional statement had been executing a second time. Problem solved, thanks for the suggestion.