On Feb 9, 2007, at 2:28 PM, Theodore H. Smith wrote:
No that's not it.
It reads one file only, and writes none. If it can't read the file, the app exits very early, it outputs about 3 lines of text before quitting.
If it can find the input file, it outputs hundreds of lines.
I can tell the difference.
The current directory has no effect on my code other than does it get the input file or not. And it's always getting the same input file.
It's like something is different causing some data structures to be written into RAM differently. Or maybe the malloc is differently linked and I'm getting some special version of malloc which is zeroing memory but only within Xcode or something like that.
Basically it's the abstract data structures that are being different, it's not IO or library stuff that's different. My app is heavily abstract data oriented, barely does any IO. (Well barely any input anyhow, lots of output. This is because it's a testing app, so it thoroughly tests the app with about 100 variations per input).